314644 - Print or Print Preview causes crash due to div with float attr

Status: RESOLVED DUPLICATE of bug 262403

(Core :: Print Preview, defect)

Description

[Nicholas Shewmaker]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

I have a PHP script that generates a page from a MySQL database.  The page loads without any problem, and is considered "Done".  I can View and Print the Source without any problem.  However, when I try to print or print preview the page, the browser races to 100% CPU, which locks it up and forces me to kill it.

I've tracked the problem down to something in the CSS.  I can either remove the "renewals" and "changes" div classes in the "Past Month" tables (but not the "current month") OR remove the float settings from the classes "renewals" and "changes" in the stylesheet.  It could be as simple as me overlooking a typo, but I have triple checked the code.

I saved the source and have attached it for review.  It is giving me the same problem as the original PHP.

Reproducible: Always

Steps to Reproduce:
1. Open attached file
2. Print or Print Preview
3.

Actual Results:  
browser locks up and must be killed

Expected Results:  
should print/preview without error

extensions installed: IEView, All-in-One Gestures, OpenBook, Adblock

I'll add my Talkback ID if that site cooperates.

Comment 1

[Nicholas Shewmaker]

Attachment: problem case

Comment 2

[timeless]

reporter: please try a 1.5 candidate or a trunk nightly...

Comment 3

[Hermann Schwab]

hang Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050910 SeaMonkey/1.0a
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b5) Gecko/20051021 Firefox/1.5

wfm seamonkey trunk

Comment 4

[Adam Guthrie]

This is probably fixed in 1.5, but a stacktrace could help us find a bug to dupe it as. Could you post the talkback ID anyway, Nicholas?

Comment 5

[Nicholas Shewmaker]

I loaded 1.5rc1 (onto a different machine), and printed the attached case both with and without using Print Preview.  I didn't get any printing errors, but the preview and output are horribly off.  In case you can't see it for yourself, the "October" numbers run 1-17 on page 1, then 1-15 on page 2.  There are only 30, so it looks like 16 and 17 are being duplicated as 1 and 2. Also, the thead is repeated twice on page 2.

I'm sorry, I didn't right down the Talkback ID because I thought I could cause another one.  I've tried searching the database, but it is being fussy.  If you have any better way to look it up, it's submitted under this same email address.

Comment 6

[Adam Guthrie]

You should be able to open up talkback and copy the talkback ID. It should be in Program Files\Mozilla Firefox\components\ and named talkback.exe (this will be on the machine with 1.0.7 on it).

Comment 7

[Nicholas Shewmaker]

Got it! Thanks.

Talkback ID: TB11329483Z

Comment 8

[timeless]

Incident ID: 11329483
Stack Signature	nsBlockFrame::DrainOverflowLines 353ead12
Product ID	Firefox10
Build ID	2005091517
Trigger Time	2005-11-01 09:33:33.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	firefox.exe + (002294ce)
URL visited	
User Comments	For some reason, using either Print or Print Preview on a PHP script are causing a crash. If I remove parts of the CSS, everything works (but is, of course, formatted wrong). The troublesome CSS is div.renewals { float: left; width: 45%; }
Since Last Crash	207832 sec
Total Uptime	207832 sec
Trigger Reason	Access violation
Source File, Line No.	c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 4323
Stack Trace 	
nsBlockFrame::DrainOverflowLines  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 4323]
nsBlockFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 807]
nsBlockReflowContext::ReflowBlock  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockReflowContext.cpp, line 547]
nsBlockFrame::ReflowFloat  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 5057]
nsBlockReflowState::FlowAndPlaceFloat  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockReflowState.cpp, line 865]
nsBlockReflowState::AddFloat  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockReflowState.cpp, line 672]
nsLineLayout::ReflowFrame  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsLineLayout.cpp, line 1051]
nsBlockFrame::ReflowInlineFrame  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 3748]
nsBlockFrame::DoReflowInlineFrames  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 3446]
nsBlockFrame::DoReflowInlineFramesAuto  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 3347]
nsBlockFrame::ReflowInlineFrames  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 3292]
nsBlockFrame::ReflowLine  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 2456]
nsBlockFrame::ReflowDirtyLines  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 2098]
nsBlockFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsBlockFrame.cpp, line 817]
nsContainerFrame::ReflowChild  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsContainerFrame.cpp, line 982]
nsPageContentFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsPageContentFrame.cpp, line 106]
nsContainerFrame::ReflowChild  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsContainerFrame.cpp, line 982]
nsPageFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsPageFrame.cpp, line 214]
nsContainerFrame::ReflowChild  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsContainerFrame.cpp, line 982]
nsSimplePageSequenceFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsSimplePageSequence.cpp, line 429]
nsBoxToBlockAdaptor::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsBoxToBlockAdaptor.cpp, line 884]
nsBoxToBlockAdaptor::DoLayout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsBoxToBlockAdaptor.cpp, line 626]
nsBox::Layout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsBox.cpp, line 1016]
nsBox::Layout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsBox.cpp, line 1016]
nsGfxScrollFrameInner::LayoutBox  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsGfxScrollFrame.cpp, line 1264]
nsGfxScrollFrame::DoLayout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsGfxScrollFrame.cpp, line 1273]
nsBox::Layout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsBox.cpp, line 1016]
nsGfxScrollFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsGfxScrollFrame.cpp, line 873]
nsContainerFrame::ReflowChild  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsContainerFrame.cpp, line 982]
ViewportFrame::Reflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsViewportFrame.cpp, line 249]
PresShell::InitialReflow  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/layout/html/base/src/nsPresShell.cpp, line 2804]
nsPrintEngine::ReflowPrintObject  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsPrintEngine.cpp, line 2796]
nsPrintEngine::ReflowDocList  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsPrintEngine.cpp, line 2553]
nsPrintEngine::SetupToPrintContent  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsPrintEngine.cpp, line 2364]
nsPrintEngine::DocumentReadyForPrinting  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsPrintEngine.cpp, line 2177]
nsPrintEngine::PrintPreview  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsPrintEngine.cpp, line 1258]
DocumentViewerImpl::PrintPreview  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsDocumentViewer.cpp, line 3252]
XPTC_InvokeByIndex  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp, line 102]
XPCWrappedNative::CallMethod  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappednative.cpp, line 2034]
XPC_WN_CallMethod  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 1781]
js_Invoke  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/jsinterp.c, line 955]
js_Interpret  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/jsinterp.c, line 2999]
js_Invoke  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/jsinterp.c, line 972]
js_InternalInvoke  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/jsinterp.c, line 1049]
JS_CallFunctionValue  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/js/src/jsapi.c, line 3698]
nsJSContext::CallEventHandler  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/dom/src/base/nsJSEnvironment.cpp, line 1297]
GlobalWindowImpl::RunTimeout  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 5491]
GlobalWindowImpl::TimerCallback  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 5853]
nsAppShellService::Run  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 495]
main  [c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 58]
kernel32.dll + 0x16d4f (0x7c816d4f)


*** This bug has been marked as a duplicate of 262403 ***

Comment 9

[timeless]

reporter: i'm very confused. the bug to which i've resolved this as a duplicate was not fixed on the 1.7 branch where you see your crash. it was fixed in time for 1.8 where you afaik have been *unable* to reproduce the crash. why do you think this bug should be reopened. or why do you think you need a new bug?

Comment 10

[Nicholas Shewmaker]

(In reply to comment #9)
> reporter: i'm very confused. the bug to which i've resolved this as a duplicate
> was not fixed on the 1.7 branch where you see your crash. it was fixed in time
> for 1.8 where you afaik have been *unable* to reproduce the crash. why do you
> think this bug should be reopened. or why do you think you need a new bug?
> 

I saw the problem on 1.0.7 but not on 1.5rc1.  I'm not sure where 1.8 comes into play.  Does that answer your question?

Comment 11

[Boris Zbarsky [:bzbarsky]]

> I'm not sure where 1.8 comes into play.

1.8 is the version of the layout engine that Firefox 1.5 uses.  Similarly, if you look at the UA string for Firefox 1.0.7:

  Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
  Gecko/20050915 Firefox/1.0.7

You can see that this is using the layout engine "Gecko", version 1.7.12 (rv:1.7.12), compiled on September 15, 2005 (20050915).

Comment 12

[Nicholas Shewmaker]

(In reply to comment #11)

The Print/Preview no longer causes a crash, but output on both is grossly inaccurate according to both the code and the on-screen display.  I am prepared to file a new bug, if need be.

Comment 13

[Boris Zbarsky [:bzbarsky]]

Yes, file a new bug.  Note, though, that printing and screen display can differ for many legitimate reasons, including styling on the page itself, pagination, etc.  So please make sure that any HTML/CSS/JS/whatever involved is either linked from the new bug or attached to it.  And please clearly describe exactly what's wrong with the print output.

cc me on the new bug, please.