Closed Bug 614146 Opened 14 years ago Closed 12 years ago

Intermittent mochitest-3 Shutdown | application timed out after 330 seconds with no output, under mozilla::dom::workers::RuntimeService::Cleanup()

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: hang, intermittent-failure) 

Rather like bug 554111 (so much like it that people have been piling mochitest failures on there since last July), but since the three from this sudden spurt that are in front of me are all 10.6, it may be something different.

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290474043.1290476743.10487.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitests-3/5 on 2010/11/22 17:00:43
s: talos-r3-snow-009

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290474320.1290476084.7593.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on 2010/11/22 17:05:20
s: talos-r3-snow-044

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290459962.1290461646.4464.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on 2010/11/22 13:06:02
s: talos-r3-snow-004
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1290659847.1290662540.19968.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitests-3/5 on 2010/11/24 20:37:27 
s: talos-r3-snow-051
TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks!
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1296020686.1296022349.31599.gz

Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on 2011/01/25 21:44:46 
s: talos-r3-snow-030
TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
Filed bug 701942 for all the Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test mochitests-3/5 failures that are ending up here.
Depends on: 701942
(In reply to TinderboxPushlog Robot from comment #133)
> Ms2ger%gmail.com
> https://tbpl.mozilla.org/php/getParsedLog.php?id=7628778&tree=Mozilla-Inbound
> Rev3 Fedora 12 mozilla-inbound debug test mochitests-1/5 on 2011-11-29
> 01:18:06
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> PROCESS-CRASH | Shutdown | application crashed (minidump found)
> Thread 0 (crashed)

(In reply to TinderboxPushlog Robot from comment #132)
> zpao
> https://tbpl.mozilla.org/php/getParsedLog.php?id=7616124&tree=Fx-Team
> Rev3 Fedora 12x64 fx-team debug test mochitests-1/5 on 2011-11-28 13:35:53
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> PROCESS-CRASH | Shutdown | application crashed (minidump found)
> Thread 0 (crashed)

(In reply to TinderboxPushlog Robot from comment #131)
> philor
> https://tbpl.mozilla.org/php/getParsedLog.php?id=7597006&tree=Mozilla-Inbound
> Rev3 Fedora 12x64 mozilla-inbound debug test mochitests-1/5 on 2011-11-26
> 13:19:57
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> PROCESS-CRASH | Shutdown | application crashed (minidump found)
> Thread 0 (crashed)

(In reply to TinderboxPushlog Robot from comment #129)
> mbrubeck%mozilla.com
> https://tbpl.mozilla.org/php/getParsedLog.php?id=7558867&tree=Mozilla-Inbound
> Rev3 Fedora 12x64 mozilla-inbound debug test mochitests-1/5 on 2011-11-23
> 15:21:57
> 
> TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds
> with no output
> PROCESS-CRASH | Shutdown | application crashed (minidump found)
> Thread 0 (crashed)

Note that all these have

ASSERTION: Profile change cancellation.: 'Error', file /builds/slave/m-in-lnx64-dbg/build/toolkit/xre/nsXREDirProvider.cpp, line 783

which doesn't seem to have happened in previous failures in this bug.
Depends on: 715137
No longer depends on: 701942
https://tbpl.mozilla.org/php/getParsedLog.php?id=8875199&tree=Mozilla-Aurora
Rev3 WINNT 5.1 mozilla-aurora debug test mochitests-3/5 on 2012-01-27 02:15:53 PST for push 62fc7d5a3085
Comment 460 is that rare miracle, a Windows shutdown hang that actually has a stack. Personally, I'd like to blame the dom workers bits in the stack, but that's bias, not any knowledge or ability to decipher stacks.

So, we have three things thrown in here: a Linux-only mochitest-1 hang with media/'s fingers all over it, a WinXP mochitest-3 hang where I suspect dom workers, and infrequent Mac 10.7 hangs which always seem to have the Bluetooth Keyboard Setup dialog up. Smells like three separate bugs to me.
Let's just blame bent for the winxp one, shall we?
Component: Mochitest → DOM
Product: Testing → Core
QA Contact: mochitest → general
Summary: Intermittent mochitest Shutdown | application timed out after 330 seconds with no output → Intermittent WinXP mochitest-3 Shutdown | application timed out after 330 seconds with no output under mozilla::dom::workers::RuntimeService::Cleanup()
(SM 2.10a1)
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1328603770.1328607648.28265.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test mochitests-3/5 on 2012/02/07 00:36:10
{
...
Thread 0
...
11  xul.dll!mozilla::dom::workers::RuntimeService::Cleanup() [RuntimeService.cpp:b077059c575a : 1053 + 0xd]
...
}
Keywords: crash
Summary: Intermittent WinXP mochitest-3 Shutdown | application timed out after 330 seconds with no output under mozilla::dom::workers::RuntimeService::Cleanup() → Intermittent mochitest-3 Shutdown | application timed out after 330 seconds with no output, under mozilla::dom::workers::RuntimeService::Cleanup()
Version: unspecified → Trunk
Keywords: crash → hang
Even a blind Linux64 finds a RuntimeService::Cleanup() every now and then :)
Victory!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Blocks: 786987
This continues to fail, most of the time, on esr10, I just figure nobody actually cares to know that.
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.