Closed
Bug 347362
Opened 18 years ago
Closed 18 years ago
PDF files cause Firefox to lock up
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nathana, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 When trying to view *.pdf files, the first one I pull up will load just fine. The second one will crash Firefox about 60-80% of the time. This is a new problem for me and has only started happening after the last upgrade. Reproducible: Sometimes Steps to Reproduce: 1.open a *.pdf file from a site that causes a new window to open (e.g. http://www.tannoy.com) 2.in the first browser window, find another *.pdf file and click (it should open in the same page as the last *.pdf) 3.Firefox crashes and windows prompts you to end process. Actual Results: complete freeze of all windows and must force quit Expected Results: showed the next *.pdf file without crashing at least half of my work online involves *.pdf files. As much as I love and swear by firefox, if this can't be solved quickly I'm going to have to use Netscape of IE (shudders).
Comment 1•18 years ago
|
||
Do you see same problem as yours in dependency tree of meta bug 336184? https://bugzilla.mozilla.org/showdependencytree.cgi?id=336184
Comment 2•18 years ago
|
||
Which version of the Acrobat plugin are you using? You can see the version in about:plugins.
Severity: critical → major
Component: File Handling → Plug-ins
Product: Firefox → Core
QA Contact: file.handling → plugins
Version: unspecified → 1.8 Branch
Comment 3•18 years ago
|
||
No response from bug opener, even though very simple question for Plugin version... Closing as WORKSFORME.
No longer blocks: 336184
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•