Closed
Bug 359657
Opened 19 years ago
Closed 19 years ago
[FIX]Firefox crashes on businessweek
Categories
(Core :: DOM: Core & HTML, defect, P1)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla1.9alpha1
People
(Reporter: jayramj, Assigned: bzbarsky)
References
()
Details
(Keywords: crash, regression)
Attachments
(3 files, 2 obsolete files)
31.98 KB,
text/plain
|
Details | |
2.75 KB,
patch
|
sicking
:
review+
sicking
:
superreview+
|
Details | Diff | Splinter Review |
466 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061105 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061105 Minefield/3.0a1
Open following link.Firefox crashes
http://www.businessweek.com/ap/financialnews/D8L7DQR80.htm
Reproducible: Always
Steps to Reproduce:
1.Click on http://www.businessweek.com/ap/financialnews/D8L7DQR80.htm
2. Crash
3.
Actual Results:
Firefox crashes. No TB generated. Clean new profile.
Comment 1•19 years ago
|
||
wfm trunk on vista rc2
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a1) Gecko/20061105 Minefield/3.0a1 ID:2006110520 [cairo]
Comment 2•19 years ago
|
||
Regression window on Windows XP SP1:
2006110304 works
2006110323 crash
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061103 Minefield/3.0a1 ID:2006110323 [cairo]
Using a clean install of current nightly (2006110504) and clean profile Talkback does not come up.
With my regular profile: TB25581007Z
A not very useful Stack Trace:
firefox.exe + 0x2f3c6a (0x006f3c6a)
firefox.exe + 0x367f55 (0x00767f55)
Comment 3•19 years ago
|
||
Seems to be related to a script on businessweek. Works if scripts are forbidden. If the scripts from Businessweek are allowed FF crashes. TB: TB25578961H (not very informative)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061105 Minefield/3.0a1 ID:2006110504 [cairo]
![]() |
||
Comment 4•19 years ago
|
||
Crashed Camino trunk build as well. Apple crash log reports:
Thread 0 Crashed:
0 org.mozilla.camino 0x005ba514 nsSubDocumentFrame::Reflow(nsPresContext*, nsHTMLReflowMetrics&, nsHTMLReflowState const&, unsigned&) + 228
Crashlog follows.
OS: Windows XP → All
Hardware: PC → All
![]() |
||
Comment 5•19 years ago
|
||
Comment 6•19 years ago
|
||
Martijn, can you check if a debug build produces a usefull stack ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 7•19 years ago
|
||
Correct regressionwindow:
works in firefox-3.0a1.en-US.win32_20061104_0142pdt build
fails in firefox-3.0a1.en-US.win32_20061104_0347pdt build
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&filetype=match&whotype=match&sortby=Date&hours=2&date=explicit&mindate=20061104+010000&maxdate=20061104+034700&cvsroot=%2Fcvsroot
(moz.org doesn't work so I can't point at a bug atm)
Updated•19 years ago
|
Keywords: crash,
regression
Comment 8•19 years ago
|
||
(In reply to comment #7)
> Correct regressionwindow:
>
> works in firefox-3.0a1.en-US.win32_20061104_0142pdt build
> fails in firefox-3.0a1.en-US.win32_20061104_0347pdt build
>
> http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&filetype=match&whotype=match&sortby=Date&hours=2&date=explicit&mindate=20061104+010000&maxdate=20061104+034700&cvsroot=%2Fcvsroot
>
> (moz.org doesn't work so I can't point at a bug atm)
>
Crap, I took the wrong builds
The correct regressionwindow is:
works in firefox-3.0a1.en-US.win32_20061103_1449pdt build
fails in firefox-3.0a1.en-US.win32_20061104_0142pdt build
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&filetype=match&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-11-03+14%3A00%3A00&maxdate=2006-11-04+01%3A42%3A00&cvsroot=%2Fcvsroot
Comment 9•19 years ago
|
||
Bug 343730 or Bug 318592 ?
Can you make anything out of this Boris ?
![]() |
Assignee | |
Comment 10•19 years ago
|
||
I can't reproduce this with my debug builds on Linux (Firefox and Seamonkey both, pulled at MOZ_CO_DATE="Fri Nov 3 20:40:49 CST 2006"). So bug 318592 is probably not the problem...
I _can_ reproduce it with a slightly later build, though. I get:
###!!! ASSERTION: Already have an undisplayed context entry for aContent: '!GetUndisplayedContent(aContent)', file ../../../mozilla/layout/base/nsFrameManager.cpp, line 580
and
###!!! ASSERTION: node in map twice: 'Not Reached', file ../../../mozilla/layout/base/nsFrameManager.cpp, line 1658
a bunch of times, then crash in nsSubDocumentFrame::Reflow because mInnerView is null.
Looking at the stack to that first assertion, the node in question (the one that already has an undisplayed content entry) is an HTMLScriptElement. The general stack to the notification is (with some frames skipped):
PresShell::ContentAppended (aContainer is the body)
...
HTMLContentSink::NotifyAppend
SinkContext::FlushTags
HTMLContentSink::FlushPendingNotifications
nsHTMLDocument::FlushPendingNotifications
nsHTMLDocument::ResolveName
(script on the page)
nsScriptLoader::EvaluateScript
nsScriptLoader::ProcessRequest
...
nsScriptLoader::OnStreamComplete
So it looks like we're notifying twice on some content; doing that for <iframe>s is bad.
At a guess, this is a regression from bug 343730...
Blocks: 343730
![]() |
Assignee | |
Comment 11•19 years ago
|
||
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #244846 -
Flags: superreview?(bugmail)
Attachment #244846 -
Flags: review?(bugmail)
Comment on attachment 244846 [details] [diff] [review]
Fix
Thanks man!
Attachment #244846 -
Flags: superreview?(bugmail)
Attachment #244846 -
Flags: superreview+
Attachment #244846 -
Flags: review?(bugmail)
Attachment #244846 -
Flags: review+
![]() |
Assignee | |
Updated•19 years ago
|
Flags: review+
Priority: -- → P1
Product: Firefox → Core
QA Contact: general → general
Summary: Firefox crashes on businessweek → [FIX]Firefox crashes on businessweek
Attachment #244846 -
Flags: review+
![]() |
Assignee | |
Updated•19 years ago
|
Component: General → DOM
Target Milestone: --- → mozilla1.9alpha
![]() |
Assignee | |
Comment 13•19 years ago
|
||
It'd be wonderful to have a minimal-ish testcase here to add to the regression tests... I tried to create a testcase based on my understanding of the code and it doesn't crash...
Checked in on request from bz
![]() |
Assignee | |
Comment 15•19 years ago
|
||
Fixed. Still great to have a testcase. Even a non-minimal standalone one would be great; I can minimize it myself at that point...
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Comment 16•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20061106 Minefield/3.0a1 ID:2006110621 [cairo]
VERIFIED/FIXED
thanks for the quick fix Boris
Comment 17•19 years ago
|
||
Comment 18•19 years ago
|
||
I tried to include the javascript in the html file but I couldn't get that to work. I hope this is useful as it is.
![]() |
Assignee | |
Comment 19•19 years ago
|
||
Arie Paap, thank you for reducing this!
Attachment #244870 -
Attachment is obsolete: true
Attachment #244871 -
Attachment is obsolete: true
![]() |
Assignee | |
Comment 20•19 years ago
|
||
Added that testcase to mochitest.
Flags: in-testsuite? → in-testsuite+
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•