[Android] Crash with some devices on `NetStream::dispose()`

[itlancer]

Problem Description

NetStream::dispose() (or something like that, on video switching or finish playback) cause application crash with some Android devices. I cannot reproduce it with isolated sample but it 100% reproducible after few video playback attempts with some Android devices with complex AIR application with differnt video files.

Tested with latest AIR 51.2.1.5. Maybe it start happen after https://github.com/airsdk/Adobe-Runtime-Support/issues/3788 changes. I'm not sure. Issue 100% reproducible with with armv7 application builds with Android TV 11 TV box with Amlogic S905W2 CPU (device doesn't support armv8). For many other Android devices seems everything fine or it happens very rare. The same issue with Video and VideoTexture. There is no such issues using ExoPlayer/media3 or other Android video players. There is no such issues using Windows, macOS and iOS. With Linux cannot be checked because of https://github.com/airsdk/Adobe-Runtime-Support/issues/1984

Related issues: https://github.com/airsdk/Adobe-Runtime-Support/issues/3519 https://github.com/airsdk/Adobe-Runtime-Support/issues/2934 https://github.com/airsdk/Adobe-Runtime-Support/issues/2910 https://github.com/airsdk/Adobe-Runtime-Support/issues/2503 https://github.com/airsdk/Adobe-Runtime-Support/issues/2277 https://github.com/airsdk/Adobe-Runtime-Support/issues/2268 https://github.com/airsdk/Adobe-Runtime-Support/issues/2125 https://github.com/airsdk/Adobe-Runtime-Support/issues/1939 https://github.com/airsdk/Adobe-Runtime-Support/issues/1174 https://github.com/airsdk/Adobe-Runtime-Support/issues/1159 https://github.com/airsdk/Adobe-Runtime-Support/issues/646 https://github.com/airsdk/Adobe-Runtime-Support/issues/587 https://github.com/airsdk/Adobe-Runtime-Support/issues/155 https://github.com/airsdk/Adobe-Runtime-Support/issues/139 https://github.com/airsdk/Adobe-Runtime-Support/issues/92 https://github.com/airsdk/Adobe-Runtime-Support/issues/82

Steps to Reproduce

Launch application with video playback with Android device with Amlogic S905W2 CPU.

Actual Result: After few video playback you will get application crash. In LogCat log you will see error:

2025-06-09 14:51:43.668  6800-6800  DEBUG                   pid-6800                             A  Revision: '0'
2025-06-09 14:51:43.668  6800-6800  DEBUG                   pid-6800                             A  ABI: 'arm'
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A  Timestamp: 2025-06-09 14:51:43+0300
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A  pid: 6419, tid: 6741, name: Thread-157  >>> com.my.app <<<
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A  uid: 10049
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A  signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A  Cause: null pointer dereference
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A      r0  0000075a  r1  00000000  r2  00000000  r3  00007ffe
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A      r4  d65ad100  r5  eee050d0  r6  ffff8001  r7  b9ebafa8
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A      r8  00001800  r9  00001000  r10 eee050d0  r11 eee05198
2025-06-09 14:51:43.669  6800-6800  DEBUG                   pid-6800                             A      ip  00000000  sp  b9ebaf98  lr  c1a7f68d  pc  c1a7a494
2025-06-09 14:51:43.679  6800-6800  DEBUG                   pid-6800                             A  backtrace:
2025-06-09 14:51:43.679  6800-6800  DEBUG                   pid-6800                             A        #00 pc 00173494  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #01 pc 00173759  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #02 pc 0016a30d  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #03 pc 000fa92d  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #04 pc 000fa983  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #05 pc 000fa6f7  /data/app/~~2WcBR-FDgH3OYsz0b-yDpw==/com.my.app-RQWe53m5DL6BWuiKgoUk-A==/lib/arm/libCore.so (BuildId: 5241d5aed6a3480a6ce1297c6c46cd5082f9cc80)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #06 pc 000808b3  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: 7f0ce142c1bc14d13596caa7f8fc2905)
2025-06-09 14:51:43.680  6800-6800  DEBUG                   pid-6800                             A        #07 pc 00039d23  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: 7f0ce142c1bc14d13596caa7f8fc2905)

Expected Result: Video playback without crashes.

Known Workarounds

none Write your own native extensions for video playback.

[ajwfrost]

Hi @itlancer - just wondering whether you were able to check this with the test build we sent across? thanks

[itlancer]

@ajwfrost, sorry for delay. There is no crash with patch anymore. Thanks!

[itlancer]

@ajwfrost, seems the same crash happens with Windows too. We reproduce it using Windows 10 64-bit with complex 64-bit AIR application with video playback using AIR 51.2.1.5. Crash happens on video switching.

Faulting application name: MyApp.exe, version: 1.2.3.0, time stamp: 0x68397017
Faulting module name: Adobe AIR.dll, version: 51.2.1.5, time stamp: 0x68397220
Exception code: 0xc0000005
Fault offset: 0x0000000000774774
Faulting process id: 0x1a0c
Faulting application start time: 0x01dbe1053876a0fe
Faulting application path: C:\MyApp\MyApp.exe
Faulting module path: C:\MyApp\Adobe AIR\Versions\1.0\Adobe AIR.dll
Report Id: 98ac1134-c249-49bd-a9a8-da146501658c
Faulting package full name: 
Faulting package-relative application ID: 

There is no such crashes with AIR 51.2.1.3 and earlier.

[itlancer]

There is no more issues anymore using AIR 51.2.1.6. Thanks!