|
|
Rank: Newbie Groups: Member
Joined: 7/27/2026 Posts: 3
|
We're hitting an intermittent crash of the EO worker process (EOWP) in our WinForms app (.NET 4.8, Win11):
1. Page A opens a named popup: window.open(url, 'addressPopup', 'popup=yes,width=480,height=520'). We accept it in the NewWindow handler (e.Accepted = true) and host e.WebView with WebView.Create(panelHandle). 2. The popup calls window.opener.postMessage(...) and then window.close(). 3. If the user clicks and types in page A within about a second of the popup closing, the whole worker process sometimes dies — every WebView (including page A, which was never closed) gets Closed with Reason = EngineCrash, and Engine.State goes to Stopped.
Faster input after the close makes it more likely, so it looks like a race in popup teardown. Reproduces on 26.1.34 and 26.2.42, worker exe version-matched. On older builds we'd also see Runtime.Exception with "Channel disconnected, Channel_ID = N" at the same moment.
Attached: the CrashDataAvailable payload from a crash today (Message was empty, Data ~41KB), and the LogFileName diagnostic log covering the session through the crash.
Is this known? Happy to provide a repro project if useful.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,508
|
Hi, We are not aware of this issue. Can you send us a repro? Please see here for more details on sending us test projects: https://www.essentialobjects.com/forum/test_project.aspxThanks!
|
|
Rank: Newbie Groups: Member
Joined: 7/27/2026 Posts: 3
|
k sent one. thanks
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,508
|
Hi,
We did receive the test project but we haven't been able to reproduce it after about 100 attempts. You mentioned that you have the CrashDataAvailable payload file. Can you send that to us as well?
Thanks!
|
|
Rank: Newbie Groups: Member
Joined: 7/27/2026 Posts: 3
|
yes, I can send that on the contact page as well. Though just double checking, cause I had an automated button in the app that I don't think really worked. It seemed that it had to come from a keyboard event specifically. So it was, launch the pop up, fill it out and close, then click on the description textbox and just start typing.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,508
|
Hi,
This is just to let you know that we are still working on this issue. The dump file we receive does show where the crash occurred but it is related to "non client view" which usually means UI elements that are triggered by the page but not a part of the page (for example, the download bubble). However we are still not able to construct a case to hit the crash location. We will reply here again as soon as we have an update.
Thanks!
|
|