Closed Bug 420059 Opened 14 years ago Closed 14 years ago

Crash @ nsXULDocument::ResumeWalk(), possibly a regression from fix for bug 419452

Categories

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

x86
Windows Vista
defect

Tracking

()

VERIFIED FIXED
mozilla1.9beta4

People

(Reporter: MarcoZ, Assigned: neil)

Details

(Keywords: crash, regression)

The line flagged in the stack trace,
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/content/xul/document/src/nsXULDocument.cpp&rev=1.815&mark=2995#2995
nsCOMPtr<nsIURI> overlayURI = mCurrentPrototype->GetURI();
is just a copy of line 3112, furthermore mCurrentPrototype has a strong URI.

So you're not going to get far without STR in a debug build...
I can reproduce this 100% of the time using the currently latest nightly (2008022714). I have Firefox closed completely, no instance running.
1. In Thunderbird, open any bugmail.
2. Via the keyboard, I open the link at the top of bugmail.
3. Firefox opens, then crashes.
4. After clicking "Restart Firefox" in BreakPad, Firefox starts and opens the URL I clicked from within Thunderbird.

If I already have an instance running, there is no problem.
This does not reproduce with a debug build. The startup time for a debug build may be too long for the bug to surface, or some other factor may influence it.
Seeing 62 crashes (were those all you, Marco?) so blocking b4 on this for now.
Flags: blocking1.9? → blocking1.9+
Priority: -- → P1
(In reply to comment #4)
> Seeing 62 crashes (were those all you, Marco?) so blocking b4 on this for now.

No, I account for five or six of them.
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg

we're going to need a debugger to chase some things, first, is mCurrentPrototype really null? windbg can easily answer that question. Other questions can also be answered w/ creative use of bp ....
Why don't we just back out bug 419452 and deal with this after beta 4?
Neil/jst/jonas: see comment 7, and please help us resolve this by tonight?
Fix for bug 419452 backed out.
Marco: can you reproduce your crashes, or should we mark this fixed and say that the backout of 419452 did, indeed, fix this.
(In reply to comment #10)
> Marco: can you reproduce your crashes, or should we mark this fixed and say
> that the backout of 419452 did, indeed, fix this.

I can no longer reproduce this crash with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008030206 Minefield/3.0b4pre. If you mark fixed, I'll mark verified.
crash-stats also showing no crashes here for the 03/01 or 03/02 builds...
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008030206 Minefield/3.0b4pre.
Status: RESOLVED → VERIFIED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.