Welcome Guest Search | Active Topics | Sign In | Register

Memory Handling in EO.WebBrowser Options
PhilipT
Posted: Monday, August 18, 2014 4:18:28 AM
Rank: Advanced Member
Groups: Member

Joined: 2/15/2014
Posts: 52
Hi EO,

I would like to check with you if the EO.WebBrowser is subjected to a strenuous memory test. Our application uses a lot of javascipt and C# communication, back and forth. The WebView instance is created just once in its whole lifetime until the PC is rebooted or application is killed via Task manager and bringing up the application again.

Do you see any potential memory problems in doing so? Any recommended approach to avoid memory issues?

Thanks
Philip


By the way, we are using AngularJS framework on the html/js side just in case you are interested to know.
eo_support
Posted: Monday, August 18, 2014 10:18:45 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,071
Hi,

You might want to create a separate monitor process to monitor the memory usage and kill it if it runs out of control. We do not see any problem with what you do in theory but because our product is based on Chrome and Chrome is a browser, so I would not think running for an extended period of time is a priority.

Thanks!
PhilipT
Posted: Monday, August 18, 2014 10:38:18 AM
Rank: Advanced Member
Groups: Member

Joined: 2/15/2014
Posts: 52
HI,

Would you know or has anyone tried to run their application with EO.WebBrowser in 24 x 7? Our application is kiosk-based so it has to run on a 24 x 7 basis. The only time it gets re-started is if the machine is powered off which can only happen if there's a power failure.

Thanks.

eo_support
Posted: Monday, August 18, 2014 10:46:21 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,071
Hi,

We do have other customers using EO.WebBrowser for similar scenarios. The above suggestion is solely based on the fact that running for an extended period of time is not a priority for Chrome. If there is a memory issue in our code, we will be able to track it down and fix it (we did catch such issues before), but if the problem is in Chrome's code, then usually we will wait for them to fix it. Beside you have another third party JavaScript library which can also leak memory due to code problems in the script. That's why we suggest you have a monitor process.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.