Hello,
First and foremost I want to thank you in advance for having a look at my ticket, much appreciated.
I am using SEB 2.2 in a MacOS Mojave 10.14.6.
I have created a new configuration for a IELTS exam, configuration was successful but when starting the Listening exam the application crashes every time with EXC_BAD_ACCESS (SIGSEGV). Any indication what might be causing the issue?
Process: Safe Exam Browser [21953]
Path: /Applications/Inspera SEB.app/Contents/MacOS/Safe Exam Browser.app/Contents/MacOS/Safe Exam Browser
Identifier: org.safeexambrowser.Safe-Exam-Browser
Version: 2.2.2 (2BCE)
Code Type: X86-64 (Native)
Parent Process: inspera-launcher [21868]
Responsible: Safe Exam Browser [21953]
User ID: 502
Date/Time: 2021-02-17 10:23:09.214 +0100
OS Version: Mac OS X 10.14.6 (18G8022)
Report Version: 12
Bridge OS Version: 5.2 (18P4346)
Anonymous UUID: CFA4494B-7DE8-E731-3A79-681FE8670F1C
Time Awake Since Boot: 7400 seconds
System Integrity Protection: enabled
Crashed Thread: 18 Audio Decoder
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007f8860700000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [21953]
Please find attached the full core dump
Best regards,
The log shows "Parent Process: inspera-launcher". I guess this is Inspera SEB then?
We only support the official, unmodified SEB versions. You have to ask Inspera for support, they can then contact us directly if it's an issue that happens inside SEB. Or you try it again with the official SEB version and verifiy if it happens with it as well.
I confirm that it is Inspera SEB launching the SEB, but the task responsible is the SEB, I'll contact Inspera SEB, but in the meantime is there any information I can provide you that would allow you to check on your side? Because the application responsible for the EXC_BAD_ACCESS (SIGSEGV) is the Safe Exam Browser and not Inspera itself.
Looks like a crash in the browser engine, as some "Audio Decoder" crashed, which isn't a part of SEB ( "Crashed Thread: 18 Audio Decoder"). Were you playing some audio during the exam? If it's a crash of the WebKit browser engine, there's probably nothing we can do. It might help to update the used macOS version (that determines the WebKit version used by SEB). In the summer SEB a a new SEB version will be using the updated WKWebView (WebKit 2) engine, that might help as well.
I don't know if Inspera SEB is interfering with the launched SEB and if the launched SEB is modified or not. If you're not using audio in the exam, maybe their remote proctoring solution is used which decodes some audio?
Such issues probably can be only solved if we can reproduce it in the debugger. But again, we would only do that, if it happens in an original, absolutely unmodified SEB version and not started by any launcher.