App is randomly crashing due to com.zipow.videobox.share.ScreenShareServiceForSDK

I’ve updated the SDK and my app started crashing when I’m trying to use the screen sharing feature (I display the screen in my app; I don’t screen share by myself).
I’ve seen lots of DeadObjectExpection which makes me think that it started using significant amount of memory so my device is killing the app. But it’s just an assumption.
Once the app crashed, even if I try to restart it and initialise Zoom SDK again, I can see the crash (again, it’s pure random).
By going through all the logs I was able to find this critical error:

2022-03-18 17:48:48.220 18895-18895/com.myapp E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.myapp, PID: 18895 Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{f01bfcc u0 com.myapp/com.zipow.videobox.share.ScreenShareServiceForSDK}
at android.os.Handler.dispatchMessage(
at android.os.Looper.loop(
at java.lang.reflect.Method.invoke(Native Method)

Anything you can do to try to investigate it on your side?

Which Android Meeting SDK version?

To Reproduce(If applicable)
I can reproduce the crashes be re-running my app in development (debug) mode multiple times. It crashes randomly and after I make the first call to initialise the SDK.
There are no other known steps to reproduce.

Smartphone (please complete the following information):

  • Device: Samsung Tab S5e
  • OS: Android 11, One UI 3.1

Hi @vvysotskyy,

Sorry to hear you’re seeing an intermittent crash. Please provide some additional information so we can investigate:

  • How frequently is this happening?
  • Are you able to reproduce this in the SDK sample app?
  • Can you please provide the full stack trace? It looks like this may have been cut off
  • Is this only reproducible on the device listed, or have you been able to reproduce on other devices?


Hi @jon.lieblich

Thanks for the answer!

> How frequently is this happening?
There’s no pattern that I could notice. I can tell that it happens when we try to start/stop sharing the screen several times.

> Are you able to reproduce this in the SDK sample app?
I didn’t have a chance to test the sample app. I’ll let you know if I find something there.

> Can you please provide the full stack trace?
There are several stack traces. This one seems to be the main one:

E/AndroidRuntime( 2923): FATAL EXCEPTION: main
[ ] E/AndroidRuntime( 2923): Process: com.myapp
PID: 2923
[ ] E/AndroidRuntime( 2923): java.lang.IllegalArgumentException:
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
com.zipow.cmmlib.CmmTimer.callNativeTimerProc(Native Method)
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at android.os.Looper.loop(
[ ] E/AndroidRuntime( 2923): at
[ ] E/AndroidRuntime( 2923): at java.lang.reflect.Method.invoke(Native
[ ] E/AndroidRuntime( 2923): at$
[ ] E/AndroidRuntime( 2923): at
[ +159 ms] I/Process ( 2923): Sending signal. PID: 2923 SIG: 9

The stack trace I’ve shared in my question is all I’ve got related to the Also we had seen some C++ stack trace but we didn’t store it and if we see it again, I’ll share it as well.

> Is this only reproducible on the device listed, or have you been able to reproduce on other devices
I’ve managed to reproduce it on other devices. But all the devices I have are Samsung.

Hi @vvysotskyy,

Apologies, but this stack trace does not appear to be the same one as the partial trace in your initial post. Can you please elaborate on when these two different traces show up?


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.