Closed
Bug 1281646
Opened 8 years ago
Closed 7 years ago
Autophone - Android 5.0 - PROCESS-CRASH | dom/browser-element/mochitest/test_browserElement_inproc_getWebManifest.html | application crashed [@ 0xda600090]
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec+, firefox50 affected)
RESOLVED
INVALID
People
(Reporter: bc, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Intermittent?
https://treeherder.mozilla.org/#/jobs?repo=try&revision=8c7cfd5790d6d4bf7334fbc4ec438ccfb02390e4&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3&filter-searchStr=Mdb&selectedJob=22556763
TEST_UNEXPECTED_FAIL | autophone-mochitest-dom-browser-element | Test exited with return code 1
PROCESS-CRASH | dom/browser-element/mochitest/test_browserElement_inproc_getWebManifest.html | application crashed [@ 0xda600090]
https://autophone.s3.amazonaws.com/pub/mobile/try-builds/bclary%40mozilla.com-8c7cfd5790d6d4bf7334fbc4ec438ccfb02390e4/try-android-api-15-debug/mochitest-dom-browser-element-mochitests-dom-browser-element-settings.ini-1-nexus-9-2-0471ccf4-a5eb-40ca-b4a0-b4ff90d1c78c.log
Operating system: Android
0.0.0 Linux 3.10.40-ga3846f1 #1 SMP PREEMPT Thu Nov 6 01:39:45 UTC 2014 aarch64
CPU: arm
ARMv1 vendor(0x4e) part(0x4e000000) features: half,thumb,fastmult,vfpv2,edsp,neon,vfpv3,vfpv4,idiva,idivt
2 CPUs
Crash reason: SIGSEGV
Crash address: 0x0
Process uptime: not available
Thread 13 (crashed)
0 0xda600090
r0 = 0xdc4da4b3 r1 = 0x8a7213c3 r2 = 0x8a7213c3 r3 = 0xdd0dae04
r4 = 0xf02ff8ac r5 = 0x00000001 r6 = 0x00000000 r7 = 0x00000003
r8 = 0xf02ff8a4 r9 = 0x00000000 r10 = 0xf02ff930 r12 = 0xdb90c8a1
fp = 0x00000006 sp = 0xf02ff8a0 lr = 0xda600091 pc = 0xda600090
Found by: given as instruction pointer in context
tracking-fennec: ? → +
Comment 1•7 years ago
|
||
close the bug since the doc can't be found
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•