Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
Description
When an app crashes on Android it is often more difficult than on other platforms to figure out the reason for the crash, as the reason will usually be buried in thousands of lines of logging output (accessible via adb logcat). Additionally running the app in the debugger usually significantly slows down launching the app, so it’s common to run the app without the debugger.
It would be super helpful if Qt Creator would attempt to get and surface any information about a crash from logcat. This could be e.g.
- Native crashes
- Java exceptions
- App gets killed due to low memory resulting in logs like this: lowmemorykiller: Kill 'my.company.app' (12392), uid 10150, oom_score_adj 0 to free 984776kB rss, 0kB swap; reason: low watermark is breached and thrashing (1135%)
- Others?
Information about the logs generated by the first two types of crashes can be found here:
https://developer.android.com/topic/performance/vitals/crash#diagnose-crashes
Attachments
Issue Links
- is duplicated by
-
QTCREATORBUG-29936 Qt Creator should show more info when Android app crashes
- Closed