ABORT: Nesting calls to ProcessPendingRestyles? (in layout/xul/base/src/tree/src/crashtests/399715-1.xhtml)

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
9 years ago
7 years ago

People

(Reporter: kinetik, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Can't find an existing bug for this.

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1284448535.1284449032.14928.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/09/14 00:15:35
REFTEST TEST-START | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/xul/base/src/tree/src/crashtests/399715-1.xhtml
++DOMWINDOW == 163 (0614EC70) [serial = 3353] [outer = 04CE46D8]
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
REFTEST TEST-PASS | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/xul/base/src/tree/src/crashtests/399715-1.xhtml | (LOAD ONLY)
REFTEST INFO | Loading a blank page
++DOMWINDOW == 164 (05D486E0) [serial = 3354] [outer = 04CE46D8]
###!!! ABORT: Nesting calls to ProcessPendingRestyles?: '!presContext->IsProcessingRestyles()', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/layout/base/nsCSSFrameConstructor.cpp, line 11563
nsStringStats
 => mAllocCount:        1060362
 => mReallocCount:        49495
 => mFreeCount:         1047184  --  LEAKED 13178 !!!
 => mShareCount:        1383602
 => mAdoptCount:         109620
 => mAdoptFreeCount:     109618  --  LEAKED 2 !!!
NPP_Destroy
nsStringStats
 => mAllocCount:             65
 => mReallocCount:            0
 => mFreeCount:              65
 => mShareCount:            107
 => mAdoptCount:              0
 => mAdoptFreeCount:          0
nsStringStats
 => mAllocCount:             15
 => mReallocCount:            0
 => mFreeCount:              15
 => mShareCount:              7
 => mAdoptCount:              0
 => mAdoptFreeCount:          0
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/xul/base/src/tree/src/crashtests/399715-1.xhtml | Exited with code -2147483645 during test run
INFO | automation.py | Application ran for: 0:04:05.719000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpnd0ftipidlog
==> process 3996 launched child process 712
==> process 3996 launched child process 2324
INFO | automation.py | Checking for orphan process with PID: 712
INFO | automation.py | Checking for orphan process with PID: 2324
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks!
Ugh.  No stack there on aborts?  That would have made it clear what's going on...
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1284594912.1284595415.32669.gzWINNT 5.2 mozilla-central debug test crashtest on 2010/09/15 16:55:12
s: mw32-ix-slave06

TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/xul/base/src/tree/src/crashtests/399715-1.xhtml | Exited with code -2147483645 during test run
The lack of stack is probably bug 589496
Blocks: 438871
Whiteboard: [orange]
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.