Android app crashes after repeatedly plugging and unplugging controller
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
When plugging and unplugging an Android game controller repeatedly (around 15 times), the app crashes with the following log:
2023-07-28 14:50:25.722 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:30.739 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:34.607 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:38.373 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:45.393 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:46.221 23453-23531/com.retroarch.ra32 I/RetroActivity: power state = 2
2023-07-28 14:50:46.223 23453-23531/com.retroarch.ra32 I/RetroActivity: battery: level = 100, scale = 100, percent = 100.0
2023-07-28 14:50:48.525 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:51.671 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:50:56.096 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:00.152 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:11.433 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:16.229 23453-23531/com.retroarch.ra32 I/RetroActivity: power state = 2
2023-07-28 14:51:16.231 23453-23531/com.retroarch.ra32 I/RetroActivity: battery: level = 100, scale = 100, percent = 100.0
2023-07-28 14:51:20.265 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:25.747 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:32.441 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:36.438 23453-23531/com.retroarch.ra32 I/RetroArch: [Autoconf]: Gasia Co.,Ltd Game Controller for Android (121/6172) not configured, using fallback.
2023-07-28 14:51:46.238 23453-23531/com.retroarch.ra32 I/RetroActivity: power state = 2
2023-07-28 14:51:46.240 23453-23531/com.retroarch.ra32 I/RetroActivity: battery: level = 100, scale = 100, percent = 100.0
2023-07-28 14:51:53.651 23453-23472/com.retroarch.ra32 A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xec480040 in tid 23472 (Thread-2)
- OS: Android armeabi-v7a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash on Android armeabi-v7a while repeatedly plugging and unplugging the controller, then capture a native backtrace for the reported SIGSEGV. Trace the controller hotplug and fallback-configuration handling; done means the app remains stable through repeated reconnect cycles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100