Open
Bug 1889001
Opened 1 year ago
Updated 1 year ago
handle RemoteException in java_exception better in report view
Categories
(Socorro :: Webapp, defect, P2)
Socorro
Webapp
Tracking
(Not tracked)
NEW
People
(Reporter: willkg, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
With this Fenix crash report:
https://crash-stats.mozilla.org/report/index/3b9000a4-e0b3-4119-812a-bfb4b0240401
The first stacktrace has this structure:
"frames": [],
"type": "RemoteException",
"module": "android.os",
"value": "Remote stack trace:\n\tat com.android.server.content.ContentService.handleIncomingUser(ContentService.java:1308)\n\tat com.android.server.content.ContentService.registerContentObserver(ContentService.java:349)\n\tat android.content.ContentResolver.registerContentObserver(ContentResolver.java:1979)\n\tat android.database.AbstractCursor.setNotificationUri(AbstractCursor.java:410)\n\tat android.database.AbstractCursor.setNotificationUri(AbstractCursor.java:398)\n"
When that's rendered in the report view, it puts the whole value value in an h3.
We should do something different. If this value is intended to show up this way, maybe we render it as a preformatted block like we do with java_stack_trace?
| Reporter | ||
Comment 1•1 year ago
|
||
Roger: Any idea why RemoteException shows up this way where the entire stacktrace is in the value?
Flags: needinfo?(royang)
Comment 2•1 year ago
|
||
I still haven't got a chance to look into this. I'll keep the NI open and revisit when I have a chance. Thanks
Comment 3•1 year ago
|
||
Created Bug 1929102 to track Android side investigation for this issue. This way, the squad that works on crash reporting can take a look. Thanks
Flags: needinfo?(royang)
You need to log in
before you can comment on or make changes to this bug.
Description
•