Intermittent crash in chrome://mochitests/content/chrome/dom/workers/test/test_fileSubWorker.xul | Exited with code 1 during test run

RESOLVED INCOMPLETE

Status

()

defect
RESOLVED INCOMPLETE
8 years ago
2 months ago

People

(Reporter: Ehsan, Unassigned)

Tracking

({crash, intermittent-failure})

Trunk
x86
macOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

8 years ago
https://tbpl.mozilla.org/php/getParsedLog.php?id=6279402&full=1
Rev3 Fedora 12x64 mozilla-central opt test mochitest-other on 2011-09-05 05:49:41 PDT for push fc78ee766770

9409 INFO TEST-START | chrome://mochitests/content/chrome/dom/workers/test/test_fileSubWorker.xul
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/workers/test/test_fileSubWorker.xul | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:01:04.706521
INFO | automation.py | Reading PID log: /tmp/tmpEzdic_pidlog
==> process 2195 launched child process 2219
==> process 2195 launched child process 2227
==> process 2195 launched child process 2235
==> process 2195 launched child process 2237
==> process 2195 launched child process 2239
INFO | automation.py | Checking for orphan process with PID: 2219
INFO | automation.py | Checking for orphan process with PID: 2227
INFO | automation.py | Checking for orphan process with PID: 2235
INFO | automation.py | Checking for orphan process with PID: 2237
INFO | automation.py | Checking for orphan process with PID: 2239
PROCESS-CRASH | chrome://mochitests/content/chrome/dom/workers/test/test_fileSubWorker.xul | application crashed (minidump found)
Crash dump filename: /tmp/tmpWJzsbM/minidumps/0486772a-de39-3315-0880cf6d-72d53165.dmp
Operating system: Linux
                  0.0.0 Linux 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64
CPU: amd64
     family 6 model 23 stepping 10
     2 CPUs

Crash reason:  SIGSEGV
Crash address: 0x7ffef6a45668

Thread 34 (crashed)
 0  libxul.so!XPCJSContextStack::Pop [xpcthreadcontext.cpp:fc78ee766770 : 107 + 0x0]
    rbx = 0xf6a45668   r12 = 0xe8bfede0   r13 = 0xf710a278   r14 = 0x1cacb5e8
    r15 = 0x00000003   rip = 0x1b7f38d7   rsp = 0xe8bfeda0   rbp = 0xffffffe0
    Found by: given as instruction pointer in context
 1  libxul.so!nsThread::ProcessNextEvent [nsThread.cpp:fc78ee766770 : 647 + 0xf]
    rbx = 0xf710a240   r12 = 0xe8bfede0   r13 = 0xf710a278   r14 = 0x1cacb5e8
    r15 = 0x00000003   rip = 0x1bb93813   rsp = 0xe8bfedc0   rbp = 0x00000000
    Found by: call frame info
 2  libxul.so!NS_ProcessNextEvent_P [nsThreadUtils.cpp:fc78ee766770 : 245 + 0xa]
    rbx = 0xf710a240   r12 = 0xf710a258   r13 = 0x00000000   r14 = 0x00000000
    r15 = 0x00000003   rip = 0x1bb5f045   rsp = 0xe8bfee30   rbp = 0xe8bfee70
    Found by: call frame info
 3  libxul.so!nsThread::ThreadFunc [nsThread.cpp:fc78ee766770 : 272 + 0xc]
    rbx = 0xf710a240   r12 = 0xf710a258   r13 = 0x00000000   r14 = 0x00000000
    r15 = 0x00000003   rip = 0x1bb93b3d   rsp = 0xe8bfee60   rbp = 0xe8bfee70
    Found by: call frame info
 4  libnspr4.so!_pt_root [ptthread.c:fc78ee766770 : 187 + 0x6]
    rbx = 0xf47fecd0   r12 = 0xcec6ca90   r13 = 0x00000000   r14 = 0x00000000
    r15 = 0x00000003   rip = 0x1e0ebf7a   rsp = 0xe8bfeea0   rbp = 0x00000000
    Found by: call frame info
 5  libpthread-2.11.so + 0x6a39
    rbx = 0xe8bff710   r12 = 0xcec6ca90   r13 = 0x00000000   r14 = 0x00000000
    r15 = 0x00000003   rip = 0xd3606a3a   rsp = 0xe8bfeed0   rbp = 0x00000000
    Found by: call frame info
This never happened again, and we have more barriers against using XPConnect off the main thread these days.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.