Henrik RydgårdandClaude Fable 5.1 9cae1a6653 Android: Don't let a late onDestroy shut down a newer activity's native state ...

After finish(), onDestroy may arrive after a new activity has already been
created and resumed, if the user relaunches quickly. The new one sees
initialized still set and adopts the native state. The old one's onDestroy
then shut down audio and called NativeApp.shutdown(), deleting the
graphics context the new render thread was using.

Number the activities, and leave the native side alone in onDestroy if a
newer one exists.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-08 18:54:46 +02:00

..

gold

New icon images, reorganize files, update banner

2024-11-03 12:29:55 +01:00

main

Fix an issue with Exit icon not showing up in MessagePopup

2026-05-13 11:04:03 +02:00

normal

New icon images, reorganize files, update banner

2024-11-03 12:29:55 +01:00

org/ppsspp/ppsspp

Android: Don't let a late onDestroy shut down a newer activity's native state

2026-10-08 18:54:46 +02:00