Closed Bug 201211 Opened 22 years ago Closed 20 years ago

while having open a PDF file in a new window is very CPU time consuming

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 198954

People

(Reporter: jlladono, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.3) Gecko/20030327 Debian/1.3-4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.3) Gecko/20030327 Debian/1.3-4 I access from a webpage to a link which opens a new windows to view a PDF. The CPU time used is very high all the time. The high consuming process is Xfree86, so I guess that it is associated to a possible loop waiting for events between mozilla and xwindows. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Is this a problem with non-Debian Mozilla builds?
This happens on Windows, Moz 1.6 See, for example http://tube.tfl.gov.uk/content/tubemap/default.asp This in fact happens for all file types that Mozilla can't handle: I get both a new blank window and the "what to do with this file?" or "where to save?" dialog boxes. To fix this, a link such as the following should be recognized as a download file and the effect of target="_blank" overriden. <a href="foo.pdf" target="_blank"></a>
(In reply to comment #1) > Is this a problem with non-Debian Mozilla builds? Thia happens with Mozilla 1.6 Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.6) Gecko/20040401 Debian/1.6-4 CPU time consumption: a) showing a PDF file in a mozilla window, clicked in a webpage, already loaded 69.6% XFree86 17.7% mozilla-bin b) after closing the window (before, it would be similar, too) 3.8% XFree86 0.0% mozilla-bin Difference is noticeable, as my cpu 'stressess' in a) Regards, Josep
Product: Browser → Seamonkey
debian builds use gtk2 dupe of "Acrobat Plugin uses 100% CPU on GTK2 Builds" *** This bug has been marked as a duplicate of 198954 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.