Closed Bug 654766 Opened 13 years ago Closed 13 years ago

CRASH when opening any webpage in firefox that has PDF file

Categories

(Firefox :: General, defect)

3.6 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ibradleyallen, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 (.NET CLR 3.5.30729)

for several days i have observed a full crash of firefox anytime the page being viewed is displaying a .pdf document.  The tabs disappear and a dialog box comes up asking if i want to send the error report and i click yes, have done this 5 times or so in the past couple days.  i was opening a pdf document on a web page, it shows the first pdf page just fine, i was on another tab typing an email when it all went away.  everything i had typed, gone.

Reproducible: Always

Steps to Reproduce:
1. http://www.rollanet.org/~eksi/2008EPHEM.pdf
2. mozilla browser crashes
3.

Actual Results:  
after several seconds the browser crashes and a screen says an error occured, do you want to send data to mozilla.  This has happened on ANY page i have tried that is showing a PDF document

Expected Results:  
past version of mozilla shows the pdf document just fine, as does ie and chrome

It should give a dialog screen saying that an update for adobe .pdf viewer is needed, click <HERE> to get and install the update, then restart firefox to apply changes.

Im guessing that when the pdf is opened, it expects that adobe acrobat reader will open and handle putting the object into the browser, but it doesnt happen and hands off control to some invalid or null pointer.
Please post the Crash IDs from about:crashes.
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Does the issue still occur if you start Firefox in Safe Mode?
https://support.mozilla.com/en-US/kb/Safe+Mode

How about with a new, empty profile?
https://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile
Ok, i didnt know about the crash id's but i did send in the crash reports when the popup came along, in one of them i added my email so you can reference it;

After the bug report, I then tried internet explorer on the same exact website, and suprise, it did cause ie to restart every time i tried to open it, and ie had an error;  so my initial observation, i thought ie was able to open the pdf files just fine, but it wasn't.  Same thing happens with ie.  I was going to leave mozilla firefox as is and switch over to ie;

i needed to have the pdf file, i "fixed it" by going to Start, adobe reader, help, updates.  it did a check and said updates are available; i let it do those, and it took a few minutes and this is a fast pc, then it rebooted the pc.

So far it works fine.  the same web /pdf file that would crash it opens just fine in firefox.

is there some logfile of adobe pdf reader that can show what version it was and what it got upgraded to, that would help?
You can find the actual Versions of Plugins in the "Plugins" Tab in Tools/Addons.
Version: unspecified → 3.6 Branch
Reporter, please update to adobe reader X (10.0.1) or later, and Firefox 4.0.1, and retest.
ok i installed reader X 10.0.1, firefox 4.01 and tested the same site and others that crashed before, and new ones that open a pdf in the browser, and i have not found any problems so far.  

I am not able to duplicate the problem with the new versions.  Will try to make it crash with pdf files and report back if successful.
Reporter -> Any update?
Closing bug as WFM - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.