Low memory crash
Description
Two different crashes described here.
- The playlist crash (happens in a 2GB ram phone)
- The playback crash (happens in a 1GB ram phone)
Steps to reproduce
A RSS stream feed is a test to both playlist/playback crashes.
Open it in VLC-android: https://feeds.podcastmirror.com/slowgerman
Actual behavior
1. Playlist crash
2GB RAM phone, Samsung Galaxy S5 (klteduos) running lineage 16/android 9:
-
(1.1) go to podcast and click play and stay in the app or outside the app ok
-
(1.2) go to podcast and click play, right after click on the media on the bottom of the screen to go to podcast playlist and scroll on it crash
logcat:
W Adreno-GSL: <sharedmem_gpumem_alloc_id:2255>: sharedmem_gpumem_alloc: mmap failed errno 16 Device or resource busy
E Adreno-GSL: <gsl_memory_alloc_pure:1971>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.(I can't reproduce the problem anymore to make a better logcat, the phone is now dead)
- (1.3) got to podcast and click play, do something else and come back to podcast playlist later ok
Note that in this case Lineage system image was used, not Samsung.
2. Playback crash
1GB RAM phone, Samsung Galaxy J1 ACE android 5.1.1:
Crash occurs earlier. The only way to avoid crash is turning phone (screen) off right after pressing play podcast. Scenarios:
-
(2.1) click to play the podcast, wait inside vlc-app, listen a few seconds, vlc-app crash and automaticaly back to home screen with dialog box "vlc angehalten"/"vlc stopped" while still playing, playback stops only after clicking ok in this dialog box.
-
(2.2) click to play the podcast, wait outside vlc-app, in home screen, listen a few seconds, dialog box "vlc angehalten"/"vlc stopped" appears while still playing, playback stops only after clicking ok in this dialog box. crash
-
(2.3) click to play the podcast, turn phone display off immediately, works. After some time it is possible to turn on the screen again and go back to the app and it is just fine, no crashes. ok
In this case original Samsung ROM was used.
Logs
The logcat for both 2.1 and 2.2 are j1ace_play_logcats.tar.gz. Please note that in both cases a process crashed then another one took place and then this second one also crashed. The first PID is logcat_0 and the second is logcat_1 for each scenario. You can see in the logs that the OOM killer plays a role. Maybe it is possible to simulate the situation if you are able to run an emulator with very low memory available. Note: renamed the issue because the prior name was specific to scenario 1.
App version
3.2.12
Device Model and Android version
Samsung Galaxy S5 (klteduos) running lineage 16/android 9
Samsung Galaxy J1 ACE running android 5.1.1
Observation 1
Similar issues were found, but not the same. Example: #1206 (closed)
Observation 2
This post was edited to include the content from comments to 2020-08-04. You reader can skip them.