Closed
Bug 1704861
Opened 3 years ago
Closed 1 year ago
Crash in [@ js::XDRObjectLiteral<T>]
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: kbrosnan, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/a51a6e95-5aec-45c3-b607-936500210413
Reason: SIGSEGV /SEGV_MAPERR
Top 3 frames of crashing thread:
0 libxul.so mozilla::Result<mozilla::Ok, JS::TranscodeResult> js::XDRObjectLiteral< js/src/vm/JSObject.cpp:1307
1 @0xcbdffffe
2 libmozglue.so BaseAllocator::realloc memory/build/mozjemalloc.cpp:4114
|
||
Comment 1•3 years ago
|
||
The above crash report seems like a corrupted stack, but this crash, with same signature has a better stack, which is XDR decoding a script during a JSM import. However, that crash happened a bunch of times on the same phone at the same time (duplicate submissions? Is that a problem?)
The crashing line for that bug doesn't make a whole heap of sense tho, so taking with a grain of salt; the crashing address is the same for a few of those crashes (0x2f6572672f304a)
Not sure the corrupt stack is too actionable.
Severity: -- → S3
Priority: -- → P3
|
||
Updated•3 years ago
|
Blocks: sm-defects-crashes
|
||
Comment 2•1 year ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•