Open
Bug 756562
Opened 13 years ago
Updated 1 years ago
[Firefox] browser-chrome: 3 sessionstore tests trigger "ASSERTION: aIndex is out of range: 'aIndex < mLength'"
Categories
(Firefox :: Session Restore, defect)
Tracking
()
NEW
People
(Reporter: sgautherie, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: assertion)
https://tbpl.mozilla.org/php/getParsedLog.php?id=11869298&tree=Firefox&full=1
Rev3 WINNT 6.1 mozilla-central debug test mochitest-other on 2012-05-18 10:07:38 PDT for push 3b86eaa02d91
{
TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_522545.js | running
###!!! ASSERTION: aIndex is out of range: 'aIndex < mLength', file e:/builds/moz2_slave/m-cen-w32-dbg/build/docshell/shistory/src/nsSHistory.cpp, line 957
###!!! ASSERTION: aIndex is out of range: 'aIndex < mLength', file e:/builds/moz2_slave/m-cen-w32-dbg/build/docshell/shistory/src/nsSHistory.cpp, line 957
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_522545.js | userTypedValue was set when changing gURLBar.value
###!!! ASSERTION: aIndex is out of range: 'aIndex < mLength', file e:/builds/moz2_slave/m-cen-w32-dbg/build/docshell/shistory/src/nsSHistory.cpp, line 957
TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_597071.js | Console message: [JavaScript Warning: "XUL box for _moz_generated_content_after element contained an inline #text child, forcing all its children to be wrapped in a block." {file: "chrome://browser/content/browser.xul" line: 0}]
###!!! ASSERTION: aIndex is out of range: 'aIndex < mLength', file e:/builds/moz2_slave/m-cen-w32-dbg/build/docshell/shistory/src/nsSHistory.cpp, line 957
INFO TEST-END | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_624727.js | finished in 704ms
}
NB: Afaict, the related (MSVC10...) stack is useless.
Comment 1•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Comment 2•1 years ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(dao+bmo)
You need to log in
before you can comment on or make changes to this bug.
Description
•