Closed Bug 614734 Opened 14 years ago Closed 11 years ago

Intermittent timeout in parser/htmlparser/tests/mochitest/test_bug599584.html or test_bug594730.html | application timed out after 330 seconds with no output

Categories

(Core :: DOM: HTML Parser, defect)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

(Keywords: intermittent-failure) 

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290648771.1290650243.3411.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitests-4/5 on 2010/11/24 17:32:51

96526 INFO TEST-START | /tests/parser/htmlparser/tests/mochitest/test_bug599584.html
NEXT ERROR TEST-UNEXPECTED-FAIL | /tests/parser/htmlparser/tests/mochitest/test_bug599584.html | application timed out after 330 seconds with no output
Can't trigger Breakpad, just killing process
INFO | automation.py | Application ran for: 0:14:57.238231
INFO | automation.py | Reading PID log: /var/folders/H5/H5TD8hgwEqKq9hgKlayjWU+++TM/-Tmp-/tmpAd3hxApidlog
NEXT ERROR PROCESS-CRASH | /tests/parser/htmlparser/tests/mochitest/test_bug599584.html | application crashed (minidump found)
Operating system: Mac OS X
                  10.6.2 10C540
CPU: amd64
     family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXC_BREAKPOINT / 0x00000002
Crash address: 0x10303de7a

NEXT ERROR Thread 0 (crashed)
 0  libSystem.B.dylib + 0x60e7a
    rbx = 0x5fbfbb0c   r12 = 0x00000000   r13 = 0x09d5a160   r14 = 0x5fbfbf88
    r15 = 0x5fbfbbb0   rip = 0x0303de7a   rsp = 0x5fbfbaf8   rbp = 0x5fbfbb20
    Found by: given as instruction pointer in context
 1  libSystem.B.dylib + 0x9e0a9
    rip = 0x0307b0aa   rsp = 0x5fbfbb00
    Found by: stack scanning
 2  libnptest.dylib!hangPlugin [nptest.cpp:50795657150e : 2833 + 0x4]
    rip = 0x09cd8845   rsp = 0x5fbfbb30
    Found by: stack scanning
 3  libnptest.dylib!scriptableInvoke [nptest.cpp:50795657150e : 1624 + 0x15]
    rip = 0x09cd5d56   rsp = 0x5fbfbb40
    Found by: call frame info
 4  XUL!mozilla::plugins::PluginScriptableObjectChild::AnswerInvoke [PluginScriptableObjectChild.cpp:50795657150e : 710 + 0x2e]
    rbx = 0x5fbfc020   r12 = 0x5fbfbe00   r13 = 0x00000000   rip = 0x00d0f3cc
    rsp = 0x5fbfbb70   rbp = 0x09d639b0
    Found by: call frame info
 5  XUL!mozilla::plugins::PPluginScriptableObjectChild::OnCallReceived [PPluginScriptableObjectChild.cpp : 764 + 0x24]
    rbx = 0x5fbfc020   r12 = 0x5fbfbe00   r13 = 0x0a820c70   r14 = 0x5fbfbf88
    r15 = 0xffffffc4   rip = 0x00d7cd17   rsp = 0x5fbfbd30   rbp = 0x09d639b0
    Found by: call frame info
 6  XUL!mozilla::plugins::PPluginModuleChild::OnCallReceived [PPluginModuleChild.cpp : 574 + 0xe]
    rbx = 0x5fbfc020   r12 = 0x5fbfc020   r13 = 0x00000006   r14 = 0x5fbfbf88
    r15 = 0x0a8008f0   rip = 0x00d6f097   rsp = 0x5fbfbe60   rbp = 0x0b00f630
    Found by: call frame info
 7  XUL!mozilla::ipc::RPCChannel::DispatchIncall [RPCChannel.cpp:50795657150e : 517 + 0xd]
    rbx = 0x09d2a410   r12 = 0x5fbfc020   r13 = 0x00000000   r14 = 0x5fbfc020
    r15 = 0x0a8008f0   rip = 0x00d21428   rsp = 0x5fbfbf70   rbp = 0x0b00f640
    Found by: call frame info
 8  XUL!mozilla::ipc::RPCChannel::OnMaybeDequeueOne [RPCChannel.cpp:50795657150e : 434 + 0xc]
    rbx = 0x09d2a410   r12 = 0x09d2a400   r13 = 0x00000000   r14 = 0x5fbfc020
    r15 = 0x0a8008f0   rip = 0x00d223b4   rsp = 0x5fbfbfb0   rbp = 0x0b00f640
    Found by: call frame info
 9  XUL!MessageLoop::DeferOrRunPendingTask [message_loop.cc:50795657150e : 343 + 0x8]
    rbx = 0x0a81f670   r12 = 0x5fbfc0d8   r13 = 0x00000000   r14 = 0x0a8008f0
    r15 = 0x0a8008f0   rip = 0x00e35af9   rsp = 0x5fbfc0a0   rbp = 0x5fbfe560
    Found by: call frame info
10  XUL!MessageLoop::DoWork [message_loop.cc:50795657150e : 451 + 0xa]
    rbx = 0x5fbfe560   r12 = 0x5fbfc0d8   r13 = 0x00000000   r14 = 0x0a8008f0
    r15 = 0x0a8008f0   rip = 0x00e36c71   rsp = 0x5fbfc0d0   rbp = 0x5fbfc1c0
    Found by: call frame info
11  XUL!base::MessagePumpCFRunLoopBase::RunWork [message_pump_mac.mm:50795657150e : 291 + 0x9]
    rbx = 0x0a800030   r12 = 0x0a81c580   r13 = 0x00000000   r14 = 0x0a8008f0
    r15 = 0x0a8008f0   rip = 0x00e46340   rsp = 0x5fbfc110   rbp = 0x5fbfc1c0
    Found by: call frame info
12  CoreFoundation + 0x4d270
    rbx = 0x0a8012e0   r12 = 0x0a8012f4   r13 = 0x00000000   r14 = 0x0a8008f0
    r15 = 0x0a8008f0   rip = 0x05dfd271   rsp = 0x5fbfc130   rbp = 0x5fbfc1c0
    Found by: call frame info
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1302884877.1302886112.29406.gz&fulltext=1
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitests-4/5 on 2011/04/15 09:27:57
Summary: Intermittent timeout in parser/htmlparser/tests/mochitest/test_bug599584.html | application timed out after 330 seconds with no output → Intermittent timeout in parser/htmlparser/tests/mochitest/test_bug599584.html or test_bug594730.html | application timed out after 330 seconds with no output
The stack here is a red herring. That minidump is just leftover from a plugin test, note that it's got libnptest.dylib!hangPlugin on the stack. Fixing bug 642175 would make us not leave these minidumps laying around.

Unfortunately, when we kill the browser for hanging on Mac, we can't currently generate a minidump, but since we killed it, and it exits with an error, it notices the leftover minidumps and decides that that's how the browser crashed.
Hmm, good point.

This makes me suspect whether it's just us hanging somewhere in the HTML5 parser code.

Henri, does the HTML parser have some kind of locking or something similar which can cause it to hang?
Whiteboard: [orange]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.