Closed Bug 819138 Opened 12 years ago Closed 11 years ago

Intermittent test_aboutmemory.xul | application timed out after 330 seconds with no output

Categories

(Toolkit :: about:memory, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

Details

(Keywords: hang, intermittent-failure)

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test mochitest-other on 2012-12-03 11:29:57 PST for push d8c788ff2545

slave: talos-r4-snow-045

https://tbpl.mozilla.org/php/getParsedLog.php?id=17563255&tree=Mozilla-Inbound

Just the highlights, since quite a lot of output...

{
###!!! ASSERTION: Invalid value for explicit/js/compartment(http://too-big.com/)/stuff: 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for explicit/(2 tiny): 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for explicit/(2 tiny)/neg1: 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for explicit/(2 tiny)/heap-unclassified: 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for other1: 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for other2: 'false', file aboutMemory.js, line 0
...
###!!! ASSERTION: Invalid value for other3: 'false', file aboutMemory.js, line 0
...
<and so on>
...
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/toolkit/components/aboutmemory/tests/test_aboutmemory.xul | application timed out after 330 seconds with no output
}
These assertion failures are expected, they arise from deliberately bogus values in the test.  They're triggered like this:

  let debug = Cc["@mozilla.org/xpcom/debug;1"].getService(Ci.nsIDebug2);
  if (debug.isDebugBuild) {
    debug.assertion(aMsg, "false", "aboutMemory.js", 0);
  }

So perhaps the assertions aren't the problem, but they look suspicious so you included them?  The real issue is the hang...
(In reply to Nicholas Nethercote [:njn] from comment #1)
> So perhaps the assertions aren't the problem, but they look suspicious so
> you included them?  The real issue is the hang...

Correct :-)
Keywords: assertionhang
Summary: Intermittent test_aboutmemory.xul | application timed out after 330 seconds with no output ("ASSERTION: Invalid value for explicit/js/compartment(http://too-big.com/)/stuff: 'false', file aboutMemory.js, line 0" and several other assertions) → Intermittent test_aboutmemory.xul | application timed out after 330 seconds with no output
The hang happens (IIUC) when the actual output doesn't match the expected output.  I've seen this occasionally happen when a new memory reporter gets registered mid-test, which screws things up.  It's possible that patch 2 in bug 848560 will fix this, by preventing new reporters from being reported mid-test.
(OrangeWFM bugs not modified in > 2 months)
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.