Pexip app crash during long duration calls or multiple short duration calls

[Sreekanth1m]

Describe the bug

Pexip app crash during long duration calls or multiple short duration calls.
Issue Description: Pexip app crashes / closes during long hours or multiple short duration calls.
Issue: Only Video call and no screen sharing
OS: Android 12
H/w: NXP i.MX 8M Plus
lowmem.txt

We did test other video platform calls like zoom on same device and don’t observe similar issues.

Attached are the app and tombstone logs.

To reproduce

Make multiple video long duration calls with out re-booting the device.

Expected behavior

Pexip app should not crash.

Version

0.12.0

Additional context

No response

[drymarau]

Thanks for the log, it looks very interesting - the first call takes about 1.5 hours, but subsequent calls do not exceed 2 minute duration:

2023-04-20 15:18:43.945   592-1118  ActivityTaskManager     system_process                       I  START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pexip.sdk.sample/.SampleActivity bnds=[8,454][260,552]} from uid 10074
2023-04-20 16:43:05.392   219-219   lowmemorykiller         pid-219                              I  Kill 'com.pexip.sdk.sample' (2248), uid 10086, oom_score_adj 0 to free 130572kB rss, 33708kB swap; reason: device is low on swap (236kB < 61436kB) and thrashing (200%)

2023-04-20 16:43:15.122   592-2868  ActivityTaskManager     system_process                       I  START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pexip.sdk.sample/.SampleActivity bnds=[8,454][260,552]} from uid 10074
2023-04-20 16:44:00.831   219-219   lowmemorykiller         pid-219                              I  Kill 'com.pexip.sdk.sample' (2982), uid 10086, oom_score_adj 0 to free 121888kB rss, 15580kB swap; reason: device is low on swap (0kB < 61436kB) and thrashing (201%)

2023-04-20 16:45:51.380   592-607   ActivityTaskManager     system_process                       I  START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pexip.sdk.sample/.SampleActivity bnds=[8,454][260,552]} from uid 10074
2023-04-20 16:47:11.236   219-219   lowmemorykiller         pid-219                              I  Kill 'com.pexip.sdk.sample' (3375), uid 10086, oom_score_adj 0 to free 93080kB rss, 15792kB swap; reason: device is low on swap (0kB < 61436kB) and thrashing (210%)

2023-04-20 16:52:51.115   592-3562  ActivityTaskManager     system_process                       I  START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pexip.sdk.sample/.SampleActivity bnds=[8,454][260,552]} from uid 10074
2023-04-20 16:54:08.702   219-219   lowmemorykiller         pid-219                              I  Kill 'com.pexip.sdk.sample' (3768), uid 10086, oom_score_adj 0 to free 126288kB rss, 15720kB swap; reason: device is low on swap (0kB < 61436kB) and thrashing (200%)

oom_score_adj 0 indicates that the app is in foreground and should have a extremely low probability of getting killed by lmk.

App memory usage at the time of death seems fairly reasonable (around 130 Mb for the first call, even lower for other calls). Profiling may help rule out memory leak, but just from the memory usage I'd say it's not happening in the app itself.

My guess is that there may be some underlying OS issue at play here (leaky codecs?) because the OS appears to struggle allocating enough RAM for the app.

Are you able to provide the following info for further investigation:

• Hardware specs of the device
• adb shell free output
• Memory profiling of the app
• A list of codecs present on the device, with their names, supported formats and whether they're hardware or not

Additionally, what commit did you checkout to test this? The issue description lists 0.12.0 (released at the end of May), but the logs indicate that they were recorded earlier (Apr 20). It'd be great if you could run these tests against the latest available commit.

[Sreekanth1m]

Thanks for the response, while we work on the suggested analysis, please let us know if Pexip Android SDK has a call back when a participant leaves the conference. How the Android app knows about participant events like a new participant joined, left etc.

[drymarau]

Thanks for the response, while we work on the suggested analysis, please let us know if Pexip Android SDK has a call back when a participant leaves the conference. How the Android app knows about participant events like a new participant joined, left etc.

It's currently not available. I suggest that you open a feature request for discussion/tracking.