"ASSERTION: cannot get ptop" when running layout/base/crashtests/378325-1.html
RESOLVED
WORKSFORME
Status
()
People
(Reporter: jruderman, Unassigned)
Tracking
({assertion, intermittent-failure, testcase})
Trunk
---
x86
macOS
assertion, intermittent-failure, testcase
Points:
---
Bug Flags:
Firefox Tracking Flags
(Not tracked)
Details
Attachments
(1 attachment)
4.83 KB,
text/plain
|
Details |
Created attachment 414944 [details]
stack trace
Loading layout/base/crashtests/378325-1.html (with focus) triggers:
###!!! ASSERTION: cannot get ptop: 'ptop', file /Users/jruderman/central/dom/base/nsGlobalWindow.cpp, line 6689
ptop is null because top is null.
Comment 2•9 years ago
|
||
This run didn't cause this assertion at all: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1276548822.1276549542.31065.gz
Likewise, neither did this run: s: win32-slave17 2010-06-23 11:50a PDT, debug crashtest: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1277316072.1277317760.16451.gz#err0
Comment 4•6 years ago
|
||
This assertion is failing sporadically in a new crashtest that was checked in today. I filed bug 844525 for that.
Comment 5•6 years ago
|
||
Also, for reference, the crashtest from comment 0 here is currently marked as "asserts(0-99)": https://mxr.mozilla.org/mozilla-central/source/layout/base/crashtests/crashtests.list#148
Updated•6 years ago
|
Keywords: intermittent-failure
Summary: "ASSERTION: cannot get ptop" → "ASSERTION: cannot get ptop" when running layout/base/crashtests/378325-1.html
Whiteboard: [test marked as asserting]
Comment 6•3 years ago
|
||
Testcase no longer asserts on trunk.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: in-testsuite+
Resolution: --- → WORKSFORME
Whiteboard: [test marked as asserting]
Comment 8•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/faa7606a5613
Comment 9•3 years ago
|
||
bugherderuplift |
https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/faa7606a5613
status-b2g-v2.5: --- → fixed
Comment 10•3 years ago
|
||
removing the b2g 2.5 flag since this commit has been reverted due to an incorrect merge, sorry for the confusion
status-b2g-v2.5: fixed → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•