|
|
Rank: Newbie
Groups: Member
Joined: 5/1/2013
Posts: 3
|
When creating a new PDF document through EO.PDF, a new process named rundll32.exe is started to generate the PDF. So far so good. When disposing the HtmlToPdf session, the rundll32.exe is never disposed. Next time I generate a new PDF, the same rundll32.exe process is re-used, but if two users generate a PDF at the same time, two rundll32.exe processes are started. On multiple concurrent users, multiple rundll32.exe processes are started and never closed. Eventually my server runs out of RAM.
What to do? I've looked through all the settings and can't find a way to tell EO.PDF to shut down the rundll32 process.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Rundll32 will close automatically if it's been idle for a while. If you have two many concurrent users, then EO.Pdf will starts multiple Rundll32 to process each request. In that case you may hit the limit and it will run out of RAM. But that's only because you have too many concurrent requests. In another word, it means your server is overloaded.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 8/2/2012
Posts: 24
|
Hi,
I am having the same problem, which is: "if it's been idle for a while, then Rundll32 will NOT close automatically, in fact it remains forever open". So, if EO Pdf is unable to detect when to close the unused rundll32 processes, then is there any way for us to force closing from time to time those unused processes(using eo pdf classes) ?
Thanks in advance!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Please try to update the latest version and see if the problem still occurs. rundll32 shoud close automatically, so if it doesn't close, then it would appear to be a bug. If the latest build still doesn't fix the problem, please see if you can reproduce it. If you can reproduce it, let us know the steps and we will try to reproduce it here.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 8/2/2012
Posts: 24
|
Hi,
Indeed, it seems to close automatically, after aprox 5 minutes, so it is not a bug.
Thanks,
George
|
|