Android crash after 2-hour call session – fatal signal from GetStream NDK

[amaslanka]

Describe the bug After a 2-hour call session, the Android app crashes when the call ends and restarts itself, opening on the Chat tab. On further inspection, the crash appears to be a fatal signal from the GetStream NDK, indicating a native crash in the C/C++ library.

SDK version

• 1.4.4

To Reproduce Steps to reproduce the behavior:

1. Make a 1-on-1 call between two Android devices (or Android emulator and physical device).
2. Keep both devices plugged into a charger and do not use them for other tasks.
3. Let the call run for 2 hours.
4. Observe the app crash and logs indicate a native crash.

Expected behavior The app should end the call gracefully without crashing or restarting itself.

Device:

• Vendor and model: Mi 9T Pro (RKQ1.200826.002)
• Android version: 11

Additional context logcat.txt

[liviu-timar]

Hello,

Thank you for reporting the issue, we'll look into it and come back with updates.

[amaslanka]

Yet another report of the NDK crash - this time it happened while I tried to start a call by opening our activity that extends StreamVideoActivity. Attaching logcat from the device where the crash occurred:

Google-Pixel-6-Android-15_2025-04-24_100503.txt

[buddy-dev-1337]

@liviu-timar we've also been seeing this NDK crash rising quickly - https://github.com/GetStream/stream-video-android/issues/1388

[aleksandar-apostolov]

Hi there,

In 1.6+ we addressed one OOM and also added atomic guards on critical call apis like leave() etc.. The native crashes are hard to reproduce and we are hoping these updates will fix the issues.

Regards, Alex

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request from the original author. Please don't hesitate to comment on the bug if you have any more information for us - we will reopen it right away! Thanks for your contribution.