mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2024-12-28 02:24:35 +01:00
9ca9d073df
It was possible for sAlertMessageLock.notify() to be called before sAlertMessageLock.wait(), causing Dolphin to deadlock. In particular, this was guaranteed to happen if displayAlertMsg was called from the UI thread while the emulation activity is being destroyed, because runOnUiThread runs the passed-in anonymous function immediately when called from the UI thread. By replacing Object.wait/Object.notify with Semaphore.acquire/ Semaphore.release, it no longer matters what order the methods are called in. |
||
---|---|---|
.. | ||
app | ||
benchmark | ||
gradle/wrapper | ||
jni | ||
.gitignore | ||
build.gradle.kts | ||
code-style-java.xml | ||
gradle.properties | ||
gradlew | ||
gradlew.bat | ||
settings.gradle.kts |