Native crash (SIGSEGV/SIGABRT) on Nvidia Shield (v4.10.0.13) immediately after ImageService ResourceNotFoundEx

[ron67 3]

Description: My Emby Server running on an Nvidia Shield (Android 11) is experiencing frequent and predictable crashes the past couple of monthes.
The crashes happen in a tight loop and always seem to correlate with a client requesting a specific missing image asset. (Apple TV on remote location)

After running the logs through an AI analyzer I followed its suggestions and de-installed and re-installed the client app on the Apple TV to exclude this first and in the hope
the issue is now resolved.
Maybe this is already a known issue, not sure, but I sure would appreciate any advice or further suggestions that could pinpoint the error may it still consist later on.
I will be monitoring it further.

Note on the attached logcat (crash_log.txt): 
The logcat contains continuous logging spanning multiple days. While the file starts with timestamps from June 2nd, the actual crashes being analyzed here occurred on June 4th and can be found towards the bottom of the log file.

PS.
I tried to look up item ID 132993 via the server's web interface and by querying the '/emby/Items?Ids=132993' API endpoint (with my admin API key), but it returns {"Items":[],"TotalRecordCount":0}. This indicates that the item does not exist in the database anymore. It appears to be a stale/ghost ID being requested by a client's cache.

Conclusion: 
The server should gracefully handle a request for a non-existent asset by serving a 404 error back to the client, rather than letting the image-processing / fallback handler trigger a native runtime crash (SIGSEGV).

kind regards,
Ronald Vrijsen

Emby Server Version: 4.10.0.13 (Android Arm64 / .NET 8.0.27) Hardware: Nvidia Shield TV (Darcy)

Sequence of Events & Analysis: When monitoring the Emby server logs alongside the Android logcat (attached), a fatal pattern emerges down to the exact millisecond.

• A client (e.g., Apple TV) requests a Thumb image for a specific Item ID (in my logs, this is ID 132993).

• The Emby Server handles this and logs a ResourceNotFoundException.

• Exactly 4 to 25 milliseconds later, the server process terminates abruptly due to a Segmentation Fault (signal 11 (SIGSEGV)) handled by Android's runtime, forcing a Fatal signal 6 (SIGABRT) to kill the process.

• Querying the /emby/Items?Ids=132993 endpoint returns {"Items":[],"TotalRecordCount":0}, confirming that the requested ID no longer exists in the server's database (a ghost/stale ID cached on the client).

Logcat Backtrace Snippetcrash_log.txt
06-04 19:11:46.987 3758 6237 F libc : exiting due to SIG_DFL handler for signal 11 06-04 19:11:46.987 3758 6237 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 6237 (.NET TP Worker), pid 3758 (emby.embyserver) ... 06-04 19:11:47.588 6940 6940 F DEBUG : backtrace: 06-04 19:11:47.588 6940 6940 F DEBUG : #00 pc 000000000004e2cc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) 06-04 19:11:47.588 6940 6940 F DEBUG : #01 pc 000000000000506c /system/bin/app_process64 (art::SignalChain::Handler(int, siginfo*, void*)+1112) 06-04 19:11:47.588 6940 6940 F DEBUG : #02 pc 0000000000000690 [vdso] (__kernel_rt_sigreturn) 06-04 19:11:47.588 6940 6940 F DEBUG : #03 pc 000000000002c334 <anonymous:2d89fb4000>
 

04-06_embyserver-63916197567.txt 04-06_embyserver-63916192833.txt 04-06_embyserver-63916193086.txt 04-06_embyserver-63916195806.txt 04-06_embyserver-63916197111.txt