CMD+Q results in zoom sdk crash during zoom meeting

I have a bundled electron app using the zoom electron SDK and I’ve noticed that during Zoom meetings, if a user exits the app using CMD+Q, it results in an app crash and crash report dialog. Based on the crash report crashed thread, it appears something in the ZoomSDK layer is seg faulting leading to the crash. Here is a snippet from the crash report:

Process: MyApp [995]
Path: /Applications/
Identifier: com.electron.MyApp
Version: 1.0.2 (1.0.2)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: MyApp [995]
User ID: 501

Date/Time: 2020-05-20 11:36:27.365 -0500
OS Version: Mac OS X 10.15.4 (19E2265)
Report Version: 12
Bridge OS Version: 4.4 (17P4534)
Anonymous UUID: 1F8A3E41-D57B-2201-A91E-DDEEFEC87AAF

Sleep/Wake UUID: 626C58A1-8B0E-46BE-87BF-95EEC5AAD9AD

Time Awake Since Boot: 120000 seconds
Time Since Wake: 12000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000055

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [995]

VM Regions Near 0x55:
__TEXT 0000000108bb8000-0000000108be1000 [ 164K] r-x/r-x SM=COW /Applications/

Thread 0 Crashed:: CrBrowserMain Dispatch queue:
0 0x00000001148d5cc8 0x114790000 + 1334472
1 0x000000011489f1ac 0x114790000 + 1110444
2 0x000000011489ed9d 0x114790000 + 1109405
3 0x000000011489e625 0x114790000 + 1107493
4 libsystem_c.dylib 0x00007fff6887013c __cxa_finalize_ranges + 319
5 libsystem_c.dylib 0x00007fff68870412 exit + 55
6 libdyld.dylib 0x00007fff687c6cd0 start + 8

Here is a link to the full crash report:

Which version?
Latest Zoom SDK Electron -

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Package up an electron application using the latest zoom electron sdk
  2. Start a meeting using the packaged app
  3. Quit the app using CMD+Q

Additional context
macOS Catalina

Thanks in advance!

Hi Nitin,

Thanks for the post and thanks for providing the info. Let me forward this to the engineering team for further investigation and get back to you shortly.


Hi Nitin,

Thanks for reporting this. The engineering team was able to identify this issue, and this is caused by an unexpected way of killing the SDK instance(CMD+Q). Due to some dependencies and constraints, we might not be able to fix this crash at the moment, we will continue to investigate this and fix this when we can. Pardon the inconvenience caused by this.


Hi @Carson_Chen, thanks for the response. Is there anything we can do in the meantime to avoid presenting a crash report to our users? Any options to workaround it? We cannot gracefully quit our application so our users experience a crash due to this bug whenever they cmd+q.


Hi Nitin,

Thanks for the reply. Actually I have a good news for you. The engineering team has further investigate this issue and we will fix this in the next release.



Great news, thanks @Carson_Chen!


You may follow our Github repo for any updates and I will also keep you posted.