|
Rank: Member Groups: Member
Joined: 6/17/2018 Posts: 13
|
Hi,
I have a Windows Forms application using .NET Framework 4.8.2 and EOBrowser version v23.3.84.0 and everything works correctly!
However, when it is run several times in a row the error occurs: MapViewOfFile failed, Win32 Error: 8 in EO.Internal.ivul.lrqp(String& nrv, Int32& nrw)
I implemented webView.Engine.Stop(true) together with webView.Engine.AllowRestart = false ... but the error remains every time EOBrowser is used several times in a row
Any solution for this problem?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,217
|
Hi,
Win32 Error 8 is ERROR_NOT_ENOUGH_MEMORY.
We are not able to match
EO.Internal.ivul.lrqp(String& nrv, Int32& nrw)
To any code in build 23.3.84. Are you sure this is the version you are using?
Thanks!
|
|
Rank: Member Groups: Member
Joined: 6/17/2018 Posts: 13
|
Hello,
Yes, the version is 23.3.84.0 I'm using webView.Engine.Stop(true) command to release the used memory Is there anything else I can do?
Best regards
|
|
Rank: Member Groups: Member
Joined: 6/17/2018 Posts: 13
|
Anyone ?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,217
|
Hi,
Sorry about the delay. The best way to avoid this error is to start the engine as early as possible and do NOT stop it. We are unable to verify the exactly location of the out of memory error due to the fact that we can not match the line you posted with the version you mentioned, but the most common place of out of memory error is when engine starts since that's where it requires a large chunk of continuous memory space.
Most of the time out of memory error occurs not because you do not have enough memory, but because you do not have a single continous memory space large enough. In another word your memory space has been fragamented. Typically memory space fragmentation increases as your application continues to run and it is least fragmented when your application just starts. So if you start the engine immediately at that moment then it's less likely you will run into this error. Once started, you can continue to use it as long as you do NOT stop it.
Hope this helps.
Thanks!
|
|