#6185 closed defect (worksforme)
ANDROID: Crash when (un)plug keyboard on Asus Transformer
| Reported by: | SF/vpelletier2 | Owned by: | dafioram |
|---|---|---|---|
| Priority: | blocker | Component: | Port: Android |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
SCUMMVM versions tested: - 1.5.0 from app store - 1.6.0git2052-g46348e7 from daily builds
Android 4.1.1 (ASUS build: JRO03C.WW_epad-10.4.4.20-20121026), on TF700T.
How to reproduce: - Start scummvm until game list is shown. Optionally start a game or bring up a dialog. - Plug or unplug keyboard: after ~2s you should be back to home screen. Restoring scummvm restarts the app (black screen for ~10s, then main menu is displayed)
I believe scummvm crashes rather than just being sent to background, because on the recent app list the preview is blank. When sending scumvm to the background manually, a screenshot is visible and restoring often works (though not always - but that is another bug which I didn't try to reproduce on 1.6 yet).
Ticket imported from: #3586310. Ticket imported from: bugs/6185.
Attachments (1)
Change History (12)
comment:1 by , 11 years ago
| Summary: | ASUS transformer: scummvm crashes when (un)plugging keyboard → ANDROID: Crash when (un)plug keyboard on Asus Transformer |
|---|
comment:2 by , 11 years ago
comment:4 by , 11 years ago
| Owner: | set to |
|---|
comment:5 by , 11 years ago
vpelletier2: Thanks.
Looking at the log, the relevant section appears to be: D/ScummVM (29492): surfaceCreated D/ScummVM (29492): surfaceChanged: 1920x1128 (4) I/ScummVM (29492): ScummVM 1.6.0git2052-g46348e7 (Nov 10 2012 04:11:12) F/ScummVM (29492): Assertion failure: '!_system' in ../../src-master/src/backends/platform/android/jni.cpp:426 (static void JNI::create(JNIEnv*, _jobject*, _jobject*, _jobject*, _jobject*, _jobject*, jint, jint)) F/libc (29492): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 29535 (ScummVM)
comment:6 by , 11 years ago
fuzzie's analysis:
"The log clearly shows that we get an onDestroy on the activity, so the bug is that we don't actually shut down completely there. The documentation implies we can check isFinishing() to see if we actually got permanently destroyed, so maybe we should leave ScummVM running in that case."
Looking at replicating and will see if we can fix...
comment:7 by , 6 years ago
| Component: | → Ports |
|---|
comment:8 by , 6 years ago
| Priority: | normal → blocker |
|---|
Raising all identified crasher, hang, and memory violation bugs which I could not fully triage myself to blocker priority for the next release.
comment:9 by , 6 years ago
| Owner: | removed |
|---|
Removing all owners from release blockers so they can be reclaimed during the release process. If you are the previous owner and would graciously fix this bug for the next release, please go ahead and re-add yourself as owner.
comment:10 by , 6 years ago
| Owner: | set to |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
I am able to disconnect and reconnect my Bluetooth keyboard (#6880) both in game and at the gui and no crash happens. The keyboard works as intended. This is on my asus transformer prime tf201 on scummvm 1.9.0.1. Android version 4.1.1.
comment:11 by , 5 years ago
| Component: | Ports → Port: Android |
|---|
vpelletier: It would be useful if you could manage to get the relevant logs at this point to help determine what is happening: https://developer.android.com/tools/help/adb.html#logcat and attach them to this bug as a zipped text file.