Closed
Bug 1241030
Opened 9 years ago
Closed 8 years ago
[emulator-x86-kk] Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1447 (Chrome_ChildThr)
Categories
(Firefox OS Graveyard :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: hsinyi, Unassigned)
References
Details
(Keywords: intermittent-failure)
https://treeherder.mozilla.org/logviewer.html#?repo=b2g-inbound&job_id=3741124
I've seen this once.
Reporter | ||
Updated•9 years ago
|
Keywords: intermittent-failure
Reporter | ||
Comment 1•9 years ago
|
||
Summary: [emulator-x86-kk][Mnw] Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1447 (Chrome_ChildThr) → [emulator-x86-kk] Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1447 (Chrome_ChildThr)
Comment 2•9 years ago
|
||
Observing same crash issue on emulator-x86-kk try[1]/local container test[2] which blocking the debugging for reftest oranges on emulator-x86-kk. The reproduce rate appeared to be 100%.
[1] - https://treeherder.mozilla.org/#/jobs?repo=try&revision=4d4f0a986d68&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=17039143
[2] - https://pastebin.mozilla.org/8860772
Reporter | ||
Comment 3•8 years ago
|
||
I don't think we are going to move this on due to the latest B2G announcement.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•