Closed Bug 269396 Opened 20 years ago Closed 16 years ago

Print preview lockup with 100%CPU usage when using page-break-after CSS

Categories

(Core :: Print Preview, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ain.valtin, Unassigned)

Details

(Keywords: hang)

Attachments

(1 file)

1.70 KB, application/octet-stream
Details
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

XUL app installed into chrome which shows some html with more than one element
having page-break-after rule locks up with 100% CPU usage when tring to show
print preview. When there is only one bage-break rule the app wont lock up but
there is no bage break in print preview.

Reproducible: Always
Steps to Reproduce:
1.install attached XUL app into chrome
2.launch this app like: firefox -chrome chrome://pptest/content/
3.press "Print Preview" button
Actual Results:  
Firefox locks up with 100% CPU usage

Expected Results:  
Show print preview
Attached file test application
This is far from being a minimal testcase. Please do something that is a single
page, if possible. Or explain why it is impossible.
Component: General → Print Preview
Product: Firefox → Browser
Version: unspecified → 1.7 Branch
(In reply to comment #2)
> This is far from being a minimal testcase. Please do something that is a single
> page, if possible.

This is a minimal test case. The same html (test.html file in attached ZIP)
works OK when opened in FF tabbrowser and then selecting File -> Print preview
(print preview shows up with bage breaks). It fails when the html is shown in
XUL app's browser element. Perhaps it is the way PP is initiated in XUL app (via
PrintUtils.printPreview()) but the very same code works OK in XUL app too when
page-break-after rules are removed from html.
> This is a minimal test case.

Keywords: hang
>1.install attached XUL app into chrome
is that just a copy of the files into the chrome directory?
(In reply to comment #5)
> >1.install attached XUL app into chrome
> is that just a copy of the files into the chrome directory?

Installing an app into chrome (under Windows):
1) Copy the files into directory of your choice (usually under chrome but this
must not be the case), say c:\test\pptest\
2) Add line "content,install,url,file:///C:/test/pptest/" (without quotes and
with the right path) into file <firefox>\chrome\installed-chrome.txt (NB! there
must be an empty line in the end of this file).
3) Delete file <firefox>\chrome\chrome.rdf and restart Firefox.

To uninstall you just remove the line you added in step 2 from
installed-chrome.txt file, delete chrome.rdf file and restart Firefox.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Assignee: bross2 → printing
QA Contact: general
WFM with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4pre) Gecko/20090313 Shiretoko/3.1b4pre
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: