|
|
Rank: Newbie
Groups: Member
Joined: 6/6/2016
Posts: 3
|
I'm wondering if someone can shed light on so issues we appear to be having releasing memory after creating PdfDocument objects via a httphandler. We've watched app pool's total memory usage climb to 1.5 GB as a result of calling the handler from multiple clients. Garbage collection does not seem to occur. Only management option is to recycle the pool.
Are there any known issues or a manual disposal method we can invoke?
We are running 2015.4.18.0.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, If you use HtmlToPdf, you can try to call this method and see if it helps: http://www.essentialobjects.com/doc/eo.pdf.htmltopdf.clearresult.aspxThanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/6/2016
Posts: 3
|
No, we're not even using that. Just loading a byte array to a PdfDocument object.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, That should not cause such problems. If you continue to have problem, please try to isolate the problem into a test project and send us the test project: http://www.essentialobjects.com/forum/test_project.aspxOnce we have that we will be happy to investigate further. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/6/2016
Posts: 3
|
Thank you will do!
|
|