Closed
Bug 395253
Opened 17 years ago
Closed 17 years ago
Freezes when printing a web page from wikipedia
Categories
(Core :: Print Preview, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: walec51, Unassigned)
References
()
Details
(Whiteboard: CLOSEME (WFM)?)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Firefox freezes when trying to print or generate a print preview of this web page:
http://en.wikipedia.org/w/index.php?title=AT_Attachment&printable=yes
CPU usage goes to ~90% and it seems to allocate more and more memory.
Reproducible: Always
Steps to Reproduce:
1. Go to http://en.wikipedia.org/wiki/AT_Attachment ( page version: 09:06, 5 September 2007 Radiant! )
2. Click "Printable version" in the pages tool box (it will move you to http://en.wikipedia.org/w/index.php?title=AT_Attachment&printable=yes)
3. Try to print this page or generate a print preview
Actual Results:
Firefox freezes
Expected Results:
Print the web page
Comment 1•17 years ago
|
||
this crashes for me on Branch, but appear fixed on Trunk
could you try with a current nightly build?
Component: General → Print Preview
Product: Firefox → Core
QA Contact: general → printing
Whiteboard: CLOSEME (WFM)?
Version: unspecified → 1.8 Branch
Reporter | ||
Comment 2•17 years ago
|
||
Done some testing.
This bug is also present in the Linux version:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty)
But it doesn't appear on nightly build:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a8pre) Gecko/2007090704 Minefield/3.0a8pre
from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.0a8pre.en-US.linux-i686.tar.bz2
Comment 3•17 years ago
|
||
WFM, Firefox trunk 2007122604 on Linux and 2007122705 on Windows XP.
-> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•