Closed
Bug 1826591
Opened 2 years ago
Closed 2 years ago
Log crashes in the ExceptionHandler if logging uncaughtExceptions cause a crash
Categories
(Fenix :: General, task, P1)
Tracking
(firefox115 fixed)
RESOLVED
FIXED
115 Branch
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: jonalmeida, Assigned: jonalmeida)
References
Details
(Whiteboard: [geckoview:m115])
Attachments
(1 file)
As an extension to bug 1826590, we should catch any exceptions thrown when the crash reporter crashes and, at the minimum, log it to the console as an error.
Something as simple as adding a catch block would suffice:
try {
crashReporter.onCrash()
} catch (e: Exception) {
Log.e(TAG, "Crash reporter crashed.", e)
} finally {
terminateProcess()
}
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P1
Assignee | ||
Comment 1•2 years ago
|
||
I lost track of this task in 113 - fixing it now.
Status: NEW → ASSIGNED
Whiteboard: [geckoview:m113] → [geckoview:m115]
Comment 2•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Target Milestone: --- → 115 Branch
Comment 3•2 years ago
|
||
Authored by https://github.com/jonalmeida
https://github.com/mozilla-mobile/firefox-android/commit/6c77bcdf8dad4f950f6f2e3a5c7ab08070ab98bb
[main] Bug 1826591 - Catch and log exceptions when reporting crashes
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox115:
--- → fixed
Flags: qe-verify+
Resolution: --- → FIXED
Comment 4•2 years ago
|
||
Hello Jonathan,
Is QA verification needed for this issue? If so, could you please provide us with some steps to reproduce (STR) or testing scenarios?
Thank you!
Assignee | ||
Comment 5•2 years ago
|
||
Clearing qe-verify since there is nothing to verify. Thanks Adina!
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•