|
|
Rank: Member
Groups: Member
Joined: 6/5/2018
Posts: 14
|
We recently upgraded to Eo.webbrowser 19.1.40 but we're having trouble with eowp.exe not closing/releasing resources, resulting in eventual out of memory exceptions etc. This was not a problem previously when we were using v 18.
Are there any known issues or common troubleshooting steps we should follow to resolve this?
Sorry this is a little light on details. I am just starting to investigate this issue and came here first to check if this was a known issue.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,258
|
Hi,
We are not aware of such issues. We did change how eowp.exe closes from V18 to V19 but that affects when your session logs off. Specifically eowp.exe will attempt to prevent a session from ending when there are still active WebView objects and it will only exit after all WebViews have been destroyed. So you may want to make sure that all WebViews are destroyed properly.
If the problem persists, we will need a repro project/case in order to investigate further.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/5/2018
Posts: 14
|
Thanks for your reply. It very much looks to me as though this may be the case.
Is there any way I can programmatically detect whether there are still active WebView objects that need to be destroyed? Our software opens a number of simultaneous webviews, so I would need to be able to ensure that they are all cleaned up prior to exiting, or at least inspect them to determine how they came to be still open.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,258
|
No. You have to do this in your own code. Your code created those WebView objects and you should make sure they are properly closed/destroyed.
|
|