seb-win-refactoring: SEB 3.7.1 unexpectedly terminated

From three different systems (it is not a consistent issue, as many report no problems), I’ve gathered the following:

/* Safe Exam Browser, Version 3.7.1 (x64), Build 3.7.1.704

2024-09-18 18:13:20.380 [08] - INFO: Successfully started new client instance.
2024-09-18 18:13:20.380 [08] - INFO: Successfully activated first session 'd801310d-12d5-4b07-8bdd-a89c0d0428ee'.
2024-09-18 18:13:20.380 [08] - INFO: ### ---------------------------------------- Session Running ----------------------------------------- ###
2024-09-18 18:14:10.448 [23] - DEBUG: [RuntimeHost] Received message 'SimpleMessage -> Ping', sending response 'SimpleResponse -> Acknowledged'.
2024-09-18 18:14:20.366 [24] - DEBUG: [ClientProxy] Sending message 'SimpleMessage -> Ping'...
2024-09-18 18:14:20.369 [24] - DEBUG: [ClientProxy] Received response 'SimpleResponse -> Acknowledged' for message 'SimpleMessage -> Ping'.
2024-09-18 18:14:20.371 [24] - INFO: [ClientProxy] Pinged host, connection is alive.
2024-09-18 18:14:42.369 [23] - ERROR: Client application has unexpectedly terminated with exit code -1073741819!
2024-09-18 18:14:42.369 [23] - INFO: ### ------------------------------------- Session Stop Procedure ------------------------------------- ###
2024-09-18 18:14:42.379 [23] - INFO: Reverting kiosk mode 'CreateNewDesktop'...

Hoping the exit code from Runtime.log provides better insight in what I could pursuit next as possible cause.

Have not been able to reproduce it myself, which is making it difficult to provide additional information as I don’t like forwarding logs from end-users.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 27 (9 by maintainers)

Most upvoted comments

Finally figured out what is causing the crash.

Crash occurs immediately after window.close() is done to a pop-up that we open and have permission to close. We even delayed it for 15 seconds via setTimeout(), and it simply delays the crash for 15 seconds.

The pop-up however uses a bunch of frameworks; simple ones such as knockout and bootstrap, but also complex ones that rely on TensorFlow as well as hidden canvasses that play back video and screen recordings.

Fix for us is for us to simply not close the pop-up for the time being, but I’m going to try to boil down the issue to exactly what method/framework is causing the crash. Every handle/element should automatically be closed when a browser window is closed, but perhaps CEF or the way SEB uses CEF is creating a problem there.

Feel free to keep this issue closed until I’m able to provide you with a functional sample that consistently reproduces the issue.

Need a little more time, responding to keep ticket open.

Tried with v3.9.0.783 and still unexpectedly terminating.

Totally disabled Edge as a last resort which stopped all reference to msedgewebview2.exe in logs, but SEB still unexpectedly terminated, so back to square one.

Everything works without issues on macOS, and it does not happen to every SEB Windows users, so I’m going to create a test website from scratch that results in the same crash and then remove functionality until I narrow down the cause.

@dbuechel got sidetracked on other development, but will test v3.9.0 tomorrow. Tried the CEF by itself and that one worked fine, although it might not have been the exact same version that SEB bundles.

Have not narrowed things down to easy reproducible steps, because I’m fully aware that will be key for you to investigate the underlying source. Of course if v3.9.0 solves it then I’ll take the win and move on 😄

Finally been able to figure out the underlying cause of this crash.

It happens when SEB is the one responsible for terminating a prohibited application that relies on the msedgewebview2.exe browser control.

MS-Teams.exe for example.

Educated guess is that SEB terminating that process causes weird side-effect to the CefSharp.BrowserSubprocess.exe process that was started beforehand (both rely on Blink rendering engine). The events are visible in the Client log shared on Oct 11th, but because it showed a clean termination I never considered it to be interfering with a crash that happens much later.

Still working on testing variations to create an easier reproducible test-scenario, but having Microsoft Teams active and letting SEB close it appears to be do the job. Keeping in mind that the SEB crash (18:14:38.160 - Process has terminated) doesn’t happen until a few seconds after the successful closing of the pop-up window (18:14:18.076 - Window 2 has been closed). Not sure yet if the pop-up triggers the crash or side-effect of our usage, so plan to create test-scenarios for this.

Manually closing all the prohibited applications before starting SEB avoids the crash from happening.

Got excited by these new findings, so wanted to already re-open the issue with the info discovered, but will follow-up soon with additional details.

It has been tough scheduling with the students impacted as they’ve been exempted for the time being, so I’m forced to connect with them in their free time.

Heading to OLC 2024 conference next week but will pick this up once I return to try to get the details needed.

It indeed still persist, and I believe I’m up to 7 users now (out of thousands without any issue). My next plan of attack is to take remote control and have Microsoft SysInternal Process Monitor running to keep track of any application other than SEB that is reading into the program and user-data folders that SEB uses. There has to be something interfering. Windows Safe Mode is not easy to do remote, but going to try documenting a step-by-step guide for that as well.

The ESET Anti-Virus and Cisco WebEx comment made in another thread as known conflicts is something I’ll dig into further as well.