I have the same issue on a multi-threading windows service -> after days of debugging with help of windbg found the source of the problem to exact same endpoint htmlDocument.LoadHtml(stringInput);
Does anyone has a fix for this?
I think it is the same issue as this one http://htmlagilitypack.codeplex.com/workitem/30268 , but the fix from there does not seem very reliable :) the windows services are consuming a lot of memory after applying that fix.
It would be really great if someone who knows what is doing could fix this.