Randomly crashes on Apple Silicon #176
Comments
Translated Report (Full Report Below)Process: Safe Exam Browser [1312] Date/Time: 2022-01-12 09:28:52.2876 +0100 Sleep/Wake UUID: 66EE3493-4699-4EC3-BDF2-840186BF5098 Time Awake Since Boot: 4100 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Application Specific Backtrace 0: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.coreanimation.render-server Thread 2:: com.apple.NSURLConnectionLoader Thread 3:: com.apple.NSEventThread Thread 4:: LocalStorage Thread 5:: LocalStorage Thread 6:: JavaScriptCore libpas scavenger Thread 7:: Heap Helper Thread Thread 8:: Heap Helper Thread Thread 9:: Heap Helper Thread Thread 10:: JIT Worklist Helper Thread Thread 11: Thread 12: Thread 13: Thread 0 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Safe Exam Browser","timestamp":"2022-01-12 09:28:53.00 +0100","app_version":"3.0","slice_uuid":"d2f1a278-d9b4-3dae-9808-4c643243ec52","build_version":"343F","platform":1,"bundleID":"org.safeexambrowser.SafeExamBrowser","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.1 (21C52)","incident_id":"19488ED1-BAD3-4ECC-9FC9-663563A13600","name":"Safe Exam Browser"} ], ] |
|
Usually after a crash, macOS displays a window containing a crash log. Please copy-paste the whole text into a comment here. You can also check in the Console app in the section (left side menu) Crash Reports, there should be some with safeexambrowser in the file name, please send that. Also as when ever reporting similar technical issue, please send SEB log files. See here where to find those. Ideally always indicate the date/time when approximately the issue happened. We didn't observe any specific crashes on Apple Silicon M1 Mac Book Air, do you already have the new MacBook Pro 14" or 16" or the older M1 13"? Also, what exam system are you using? Unfortunately some systems not yet specifically supporting the new SEB Javascript API usually would use the old WebKit browser engine, which is crash prone especially when more modern Web APIs are used. All exam systems should be updated for SEB 3.0 macOS/iOS, then they would use the modern WebKit browser engine/modern WebView (WKWebView), which is much more stable and if the system web rendering process crashes, SEB itself doesn't crash. |
|
Thanks for the log. This is a bug in SEB 3.0, it should be fixed in the pre-release version 3.2pre5. In the next few weeks we'll release the final versions of SEB 3.1 for macOS/iOS which will also fix all known issues (the final release of 3.2 with built-in Zoom proctoring is sheduled for later). |
danschlet
added
the
please test
|
Thanks for your quick response. The crash report is posted above. It's the new MacBook Pro 16" (M1 Pro) and the exam system seems to be Moodle 3.11.3. I am hesitant about posting SEB log files, as they contain personal information. However, should they be absolutely necessary in order to diagnose the problem, please let me know. |
|
SEB logs only contain host, machine and user name, which you could remove, and URLs (if log level debug or higher) but you could also use a private message on our old but still active SourceForge site or an email to info at safeexambrowser . org (but only for logs or non-public access data for reproducing issues on testing accounts, we cannot answer questions by email). But in this case I don't think I need the SEB logs, hope it will work with 3.2pre5 or the upcoming versions for you. |
|
Hi! We're also encountering the same error as above and this time, we used version 3.2pre5. SEB closed on it's own after 30 to 40 min. One of our examinees was able to send the log to us seen below. Translated Report (Full Report Below)Process: Safe Exam Browser [3768] Date/Time: 2022-01-23 19:39:28.5699 +0800 Sleep/Wake UUID: 7E90EB2D-BF75-4D3B-BD0F-758C0E50E571 Time Awake Since Boot: 26000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Application Specific Backtrace 0: Kernel Triage: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.coreanimation.render-server Thread 2:: com.apple.NSURLConnectionLoader Thread 3:: com.apple.NSEventThread Thread 4:: LocalStorage Thread 5:: LocalStorage Thread 6:: JavaScriptCore libpas scavenger Thread 7:: com.apple.CFSocket.private Thread 8: Thread 9: Thread 10: Thread 0 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Safe Exam Browser","timestamp":"2022-01-23 19:39:32.00 +0800","app_version":"3.2pre5","slice_uuid":"5e983804-6df9-3d2b-80af-de8b8e7fb78c","build_version":"3632","platform":1,"bundleID":"org.safeexambrowser.SafeExamBrowser","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.0.1 (21A559)","incident_id":"C5972B69-A913-4F79-998C-A908CDFEFF04","name":"Safe Exam Browser"} ], ] Model: MacBookAir10,1, BootROM 7429.41.5, proc 8:4:4 processors, 8 GB, SMC |
|
Since the exam saves our answers in real time, the examinees are able to resume where they left off but since their exam is more than an hour long, they might encounter this issue a few times. Any fix or suggestions are appreciated! |
|
Are you also using Moodle as exam system? If not, which else? It's even stranger if the crashes happen after a long time in the exam, like the 30-40 min you mention. I don't see any reason why SEB would work 30-40 min. and then suddenly crash, as long as it's not connected to some hardware issue (overheating?) or some system or third party process which has a buffer overflow or similar after a long period and invokes this issue for SEB. Did students do any special action just when the crashes happened, like closing a browser window in SEB, navigating to a new question (maybe graphically complex, running javascript or video) or anything which might have triggered the special situation leading to the crash? Also are all of those students using some specific internet security tool, endpoint security, anti-malware scanning software etc.? |
|
Hi Daniel!
Thanks for replying!
We are also using Moodle as an exam system. What is actually strange is
that it does not seem to affect everyone with an Apple M1. I tried taking
the same exam as well (Moodle-based exam, currently using an Apple M1,
macOS 12.1) and I don’t get the same error and I can’t seem to replicate
it. I’m not sure if this is system based but we had 10 examinees from our
exam simulation error that encountered the same error. Unfortunately, only
1 was able to copy the error log and that’s what I posted earlier.
We observed the students while taking the exam (via Zoom but we prefer
using a cellphone to do this) and as far as we know, they are just running
the exam as is. All of them were using the 3.2 pre-build posted in GitHub.
The exam is not particularly graphic intense as our of 70 items, only 1-2
questions had images. Each page, though, contains 10 questions but that has
been our setting ever since last year.
Regarding internet security tools, I am not sure with regards to the
individual examinees’ setups but we do inform them to disable any
anti-virus software especially for those running Windows. We don’t seem to
have that problem with Mac devices. I have installed Sophos in my own
device and I did not encounter any errors.
Currently, we have instructed those examinees affected to either change
their device and test the exam again or they proceed with the exam as is
and just reload the exam since the answers are able to save prior to
shutting down.
Hope these information helps.
Robert Glen R. Abesamis MD DPSP
Anatomic Pathologist
Consultant Pathologist
Department of Pathology and Clinical Laboratories
Far Eastern University - Nicanor Reyes Medical Foundation
Assistant Professor
San Beda University - College of Medicine
Guest Lecturer
Ateneo School of Medicine and Public Health
On January 24, 2022 at 12:00:15 AM, Daniel R. Schneider ( ***@***.***) wrote:
Are you also using Moodle as exam system? If not, which else?
It's even stranger if the crashes happen after a long time in the exam,
like the 30-40 min you mention. I don't see any reason why SEB would work
30-40 min. and then suddenly crash, as long as it's not connected to some
hardware issue (overheating?) or some system or third party process which
has a buffer overflow or similar after a long period and invokes this issue
for SEB.
Did students do any special action just when the crashes happened, like
closing a browser window in SEB, navigating to a new question (maybe
graphically complex, running javascript or video) or anything which might
have triggered the special situation leading to the crash?
Also are all of those students using some specific internet security tool,
endpoint security, anti-malware scanning software etc.?
—
Reply to this email directly, view it on GitHub
<#176 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXNVW52KUQBTNQW457ENPYLUXQQY7ANCNFSM5LYQPLMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hi Robert, thanks for the additional information. It's definitely a strange error, I also didn't get such feedback from recent exams a partner university did with up to 1000 participants (I guess around 50% with Mac and surely a fair number of M1 Macs). Given that you're using Moodle, I guess you're also using the built-in Safe Exam Browser support (activated in Quiz settings, either with "manual" or uploaded SEB configuration)? In that case it seems like your students would have some Moodle resources or external links open in additional browser windows? I'm asking because the crash log shows that the modern WebView (WKWebView) is involved, which with default settings and the SEB-Moodle integration is currently only used for additional browser windows, not the main window where Moodle is running. I don't know if this information really helps us tracking down the issue, but still good to know. I know that it's not easy to collect log files from students, but it still would be helpful if someone who had the crash happening could send both the crash report and the SEB log files, found in the directory I will implement one small change which might prevent the crash (a bit a speculative fix, but from the crash log I at least know which method in the code actually seems to crash) and let you know when it's available (likely next week). |
|
We are using the built-in Safe Exam Browser support in Moodle. For this set
of examinees though, only Moodle should be in another tab in Google Chrome
when initially logging in the exam. We are able to check this because of
the way we do Zoom proctoring.
Based on our schedule, we may have another practice exam session this
Wednesday so should we encounter this issue again, we’ll instruct the
examinees as recommended and send you the data.
Thanks again!
Robert Glen R. Abesamis MD DPSP
Anatomic Pathologist
Consultant Pathologist
Department of Pathology and Clinical Laboratories
Far Eastern University - Nicanor Reyes Medical Foundation
Assistant Professor
San Beda University - College of Medicine
Guest Lecturer
Ateneo School of Medicine and Public Health
On January 24, 2022 at 2:18:29 AM, Daniel R. Schneider ( ***@***.***) wrote:
Hi Robert, thanks for the additional information.
It's definitely a strange error, I also didn't get such feedback from
recent exams a partner university did with up to 1000 participants (I guess
around 50% with Mac and surely a fair number of M1 Macs).
Given that you're using Moodle, I guess you're also using the built-in Safe
Exam Browser support (activated in Quiz settings, either with "manual" or
uploaded SEB configuration)? In that case it seems like your students would
have some Moodle resources or external links open in additional browser
windows?
I'm asking because the crash log shows that the modern WebView (WKWebView)
is involved, which with default settings and the SEB-Moodle integration is
currently only used for additional browser windows, not the main window
where Moodle is running. I don't know if this information really helps us
tracking down the issue, but still good to know.
I know that it's not easy to collect log files from students, but it still
would be helpful if someone who had the crash happening could send both the
crash report and the SEB log files, found in the directory /Library/Logs/Safe
Exam Browser/ ( representing the user's home directory).
I will implement one small change which might prevent the crash (a bit a
speculative fix, but from the crash log I at least know which method in the
code actually seems to crash) and let you know when it's available (likely
next week).
—
Reply to this email directly, view it on GitHub
<#176 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXNVW54CYSOCSQ47IVGA2HDUXRA7LANCNFSM5LYQPLMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I attempted to fix this in the latest preview 7 of SEB 3.1: https://github.com/SafeExamBrowser/seb-mac/releases/tag/3.1pre7 |
|
I have similar crashes on Monterey with SEB 3.0 and Modern WKWebView engine whenever the JavaScript At least in my case, this seems linked to #181. Preview 10 of SEB 3.1 works for me. |
danschlet
added
fixed in new release
and removed
please test
I've just taken an exam with SEB on my Apple Silicon MacBook Pro (2021). During the 60 minute exam the program crashed at least 5 times, in regular intervals of about 10 minutes. Other students with M1 Macs experienced the same issue.
This requires an urgent fix as it makes the program unusable. In the meantime, at least a message warning the user about issues on Apple Silicon Macs should be presented when starting up SEB.
Thankfully I was able to reenter the exam when SEB crashed, but imagine if the exam was set so that I couldn't.
SEB 3.0, macOS 12.1
EDIT: attached one one of the log files
The text was updated successfully, but these errors were encountered: