You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Transcription creates hangs on Mac Intel #1594
The transcription on my machine (Mac Mini 2018, 6 dual core i7, 64GB of RAM) keeps failing over and over again. The thing is that I do not actually need the transcription at all. Though it keeps using the ressources and end up hanging the computer then there's nothing we can do but shut down the computer.
It would be great if there was an option in the settings so we could entirely turn OFF the transcription. I try to use the software, works fine until the transcription starts, sometimes the webcam has no file then the computer hangs and from there it's technically unusable.
Expected behavior
The transcription should not fail and not make the computer hang
To Reproduce
Try to capture any editing software like Adobe Premiere during more than 5 minutes on Mac OS Sequoia on an Intel Mac
Thanks for the detailed report! We're looking into why transcription can saturate an Intel Mac and hang it; a fix will reference this issue. The option to turn automatic transcription off is tracked in #1427.
Thanks for the swift response. I found a workaround to launch the app without the transcript and I can confirm the software works perfectly fine once the transcript is out of the equation.
Thanks for confirming the workaround, @digitweaks! The fix (#1595) is in v2.3.0, released today: transcription now decodes on half the cores, at a lower priority, and no longer keeps decoding after a timeout, so it should not saturate an Intel Mac anymore. Could you try v2.3.0 with transcription on and tell us whether the machine stays responsive? The option to turn automatic transcription off is still tracked in #1427.
I tested v2.3.0 with transcription enabled. After roughly three minutes of recording, the computer became severely unresponsive though was responsive enough to initiate a restart. I have been able to quit OpenScreen hoping it would stop the process but it apparently did not. So I had to reboot as I didn’t notice any process using excessive CPU in Activity Monitor and couldn't kill the process. I had a video playing in the background, I could still hear the audio while the video was sometimes playing some frames from time to time and remained sluggish until it rebooted.
Just trying to separate what could be an hardware from software issue:
I was recording a 3440×1440 display while working on an edit on Adobe Premiere which worked fine few days ago even with the transcription failure warning. The recording did not result into a usable project, after restart of OpenScreen a previous project was automatically loaded then I had a warning that the transcription failed but that did not trigger a new lasting hang. No project is available with today's date in the Open Project menu and the .mp4 video file corresponding to the screen capture is available in the Recordings folder and only 30% filled with a viewable video data, the rest was blank / black screen.
Checking the macOS diagnostic reports revealed the Intel UHD 630 GPU hangs. At 17:59:23, a GPU reset explicitly named OpenScreen’s bundled whisper-stt-server, with the GPU render ring marked “Appears hung”. This occurred before the recording started. At 18:02:57, another GPU reset named Adobe Premiere Pro, during recording.
At 18:05:23, OpenScreen logged a recording stop-timeout, reporting that the capture helper had not exited. At 18:26:30, another GPU reset named Apple’s VTEncoderXPCServ, shortly before the restart.
I understand the Intel binary may already default to CPU-only processing, but the GPU hang report names whisper-stt-server. In the packaged JavaScript, the Intel backend is labelled whispercpp-cpu, but the initial launch does not pass --cpu; that flag appears only on a fallback path.
The reports don’t establish which component triggers the problem, but they suggest a GPU/driver hang may be involved rather than a CPU saturation.
After the reboot, I opened OpenScreen as explained above then quit it. Few minutes later without any warning signs the computer shut down abruptly. So it seems that OpenScreen starts the process but then the issue becomes independent of the app being active or not.
Activity
EtienneLescot commentedon Nov 16, 2026
Thanks for the detailed report! We're looking into why transcription can saturate an Intel Mac and hang it; a fix will reference this issue. The option to turn automatic transcription off is tracked in #1427.
fix(stt): keep whisper decoding from starving the machine
digitweaks commentedon Nov 16, 2026
Thanks for the swift response. I found a workaround to launch the app without the transcript and I can confirm the software works perfectly fine once the transcript is out of the equation.
fix(stt): keep whisper decoding from starving the machine
EtienneLescot commentedon Nov 17, 2026
Thanks for confirming the workaround, @digitweaks! The fix (#1595) is in v2.3.0, released today: transcription now decodes on half the cores, at a lower priority, and no longer keeps decoding after a timeout, so it should not saturate an Intel Mac anymore. Could you try v2.3.0 with transcription on and tell us whether the machine stays responsive? The option to turn automatic transcription off is still tracked in #1427.
digitweaks commentedon Nov 17, 2026
@EtienneLescot Sure, I let you the result in a bit
digitweaks commentedon Nov 17, 2026
@EtienneLescot Thanks! Here is a detailed report.
I tested v2.3.0 with transcription enabled. After roughly three minutes of recording, the computer became severely unresponsive though was responsive enough to initiate a restart. I have been able to quit OpenScreen hoping it would stop the process but it apparently did not. So I had to reboot as I didn’t notice any process using excessive CPU in Activity Monitor and couldn't kill the process. I had a video playing in the background, I could still hear the audio while the video was sometimes playing some frames from time to time and remained sluggish until it rebooted.
Just trying to separate what could be an hardware from software issue:
I was recording a 3440×1440 display while working on an edit on Adobe Premiere which worked fine few days ago even with the transcription failure warning. The recording did not result into a usable project, after restart of OpenScreen a previous project was automatically loaded then I had a warning that the transcription failed but that did not trigger a new lasting hang. No project is available with today's date in the Open Project menu and the .mp4 video file corresponding to the screen capture is available in the Recordings folder and only 30% filled with a viewable video data, the rest was blank / black screen.
Checking the macOS diagnostic reports revealed the Intel UHD 630 GPU hangs. At 17:59:23, a GPU reset explicitly named OpenScreen’s bundled whisper-stt-server, with the GPU render ring marked “Appears hung”. This occurred before the recording started. At 18:02:57, another GPU reset named Adobe Premiere Pro, during recording.
At 18:05:23, OpenScreen logged a recording stop-timeout, reporting that the capture helper had not exited. At 18:26:30, another GPU reset named Apple’s VTEncoderXPCServ, shortly before the restart.
I understand the Intel binary may already default to CPU-only processing, but the GPU hang report names whisper-stt-server. In the packaged JavaScript, the Intel backend is labelled whispercpp-cpu, but the initial launch does not pass --cpu; that flag appears only on a fallback path.
The reports don’t establish which component triggers the problem, but they suggest a GPU/driver hang may be involved rather than a CPU saturation.
digitweaks commentedon Nov 17, 2026
Ok, little addendum:
After the reboot, I opened OpenScreen as explained above then quit it. Few minutes later without any warning signs the computer shut down abruptly. So it seems that OpenScreen starts the process but then the issue becomes independent of the app being active or not.