343191 - Browser hangs on "print" or "print preview" of yellowpages.aol.com

Status: RESOLVED DUPLICATE of bug 255982

(Core :: Printing: Output, defect)

Description

[Peter Stein]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

Search for "hotels" in some area. Try either "print" or "print preview" on the results. Browser crashes. 100% reproducible. This happens on the Windows version of FireFox as well!!

Reproducible: Always

Steps to Reproduce:
1. Perform yellowpages search.
2. Try "print" or "print preview" on results.
3.

Comment 1

[Brian Polidoro]

I ended up with a hung browser with a spiked CPU when doing a print preview.  It hung when the print preview dialog said Preparing... .  Also there was a slow but steady increase in memory usage.  Perhaps that's the cause of the crash.  

Does it crash for you immediately or is it a delayed crash?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060629 Minefield/3.0a1 ID:2006062910 [cairo]

Comment 2

[Peter Stein]

It's pretty much immediate. FireFox becomes totally unresponsive. When the "preparing" appears the cancel button is greyed out so there isn't even a graceful way to terminate. I have to "killall firefox firefox-bin" and restart firefox. This is basic functionality, I'm surprised that none of the testing suites caught this. FWIW, IE6 has no problems with "print" or "print preview" for this url.

Comment 3

[timeless]

ok, so you used the wrong word to describe what happened, your browser hung.

Comment 4

[Philip Withnall (unavailable)]

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060628 Minefield/3.0a1
WFM.

Hung, but no crash.

Comment 5

[Peter Stein]

Ok guys, lets not get analy retentive about the terminology. From a user's perspective the program becomes unusable under the circumstance described. It's really quite irrelevant whether or not the program is still in core when there are screen artifacts because the problem is 100% reproducible and the developer to which it will be assigned will be reproducing it in order to understand the problem. So please, less banter, more common sense, and lets get rolling on a solution without degenerating into a "how many angels on the head of a pin" discussion. Thank you.

Comment 6

[Andrew Schultz]

Attachment: testcase

print previewing this hangs linux seamonkey 2006-06-30-08-trunk

Comment 7

[Andrew Schultz]

dupe of "hang (infinite loop) printing floats over page break where containing box contains no non-float items"

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