Crash in SendCommand function during interruption

Hi,
We are currently using the latest ZoomVideoSDK (version: 2.2.0) for IOS. Every time an interruption happens (Eg: user press the home button on their Ipad) while data is being send via command channel, the app crashes in the sendCommand function with an error “An abort signal terminated the process. Such crashes often happen because of an uncaught exception or 999 unrecoverable error or calling the abort, function.” @ekaansh.zoom please provide steps to resolve this issue and guidance on on how to handle interruption. The debug log can be found here https://drive.google.com/file/d/1uBOAtlySMxHJ1bI5q9nWijPHVnA9QteF/view?usp=sharing . Please reply at your earliest convenience

Hi,
@ekaansh.zoom and @elisa.zoom, are there any update on the issue?

Hi @prw3100,

Can I also have the full crash log for this issue?

Thanks.

Hi @boonjun.tan,
Attached is the snippet of the thread that crashed. I have partially symbolicated our code


Please let me know if this would suffice. For security reasons, we are unable to share the whole crash log. From the screenshot you would see that the last call from our codebase was to Zoom’s CommandChanel?.sendCommand() (LINE 19 in the screenshot). The Zoom Video SDK (screenshot) used when the crash occurred was v1.12.0. The same crash happens in the latest version as well

Hi @prw3100,

We have looked over the crash thread and the SDK logs you sent us, but we aren’t able to figure out the root cause of the issue. Can you also send us the steps to reproduce this issue and also a video to reproduce the issue.

We will also need the crash log from Apple’s side to determine what is the issue as the crash thread screenshot itself is insufficient for us to investigate what is the issue and our SDK logs stopped writing when the crash happens so we cannot see what has happen completely.

Hi @boonjun.tan,
To reproduce the issue, you can simulate a scenario where a large volume of data (several minutes’ worth) is sent through the command channel on the main thread. While this transmission is ongoing, backgrounding and foregrounding the app multiple times can help trigger the problem.

Unfortunately, we’re unable to share a video as it contains proprietary material. Additionally, to reproduce the issue consistently we have a database with significant amount of data that we populated, and when two users join a meeting, all this data is exchanged. A video in this case wouldn’t be useful, especially since the UI does not indicate that data is being transmitted during this time. All you would see is 2 people join the meeting and one person backgrounds and then foreground the app, causing it to crash

We’re committed to resolving this issue and are happy to provide the full crash report. Is there a dedicated email address we could send it to instead of posting it publicly on the forum?

Thanks!

Hi @prw3100,

I will pm you directly for the crash report.

1 Like