[Android] retroarch crashes when locking device with active MupenPlus-Next core

Sorry if this was already reported, I wasn't able to find it. I don't know if this is a problem with the core or not, but I very rarely update cores, and I don't remember this in old builds of retroarch.

Description

When I minimize retroarch or lock my device while playing MupenPlus-Next, upon restoring retroarch crashes.

Steps to reproduce the bug

1. load MupenPlus-Next core and some game
2. Minimize retroarch or lock your device
3. If you've locked device, simple unlock it and retroarch will crash. If you've minimized, restrore window and retroarch crashes.

Version/Commit

You can find this information under Information/System Information
Build Date: May 27 2020

• Git Version: 02bc3ee
• Compiler: Clang/LLVM (8.0.7)
• RetroArch: 1.8.8

Environment information

• Device: Xiaomi Mi 9T
• OS: Android 10, MIUI 11.0.5

When I repeat this several times, my phone asks if I want to send report to xiaomi, but I guess it will be more usable here. Sorry for screenshot, but I wasn't able to copy this text, and I don't know if it is saved anywhere in the system:

No source file or test is named. Start by reproducing the crash on Android 10 with RetroArch 1.8.8, MupenPlus-Next, and the listed Xiaomi device, then inspect the supplied backtrace and relevant resume/restore path. Done means restoring the app after locking or minimizing no longer crashes, with a regression test if the project’s existing Android tests cover this path.