Closed Bug 592061 Opened 14 years ago Closed 11 years ago

Crash after loading pdf-file, hitting Back button and hitting Reload

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: discoleo, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows NT 5.0; rv:2.0b4) Gecko/20100818 Firefox/4.0b4
Build Identifier: Mozilla/5.0 (Windows NT 5.0; rv:2.0b4) Gecko/20100818 Firefox/4.0b4

Firefox 4.0 Beta 4 crashed while hitting the reload button. The crash reporter was not able to submit a crash report. Tried twice - reproducible. Steps are outlined below.

Reproducible: Always

Steps to Reproduce:
1. go to http://cran.R-project.org
2. in the documentation Menu, select Manuals
3. on the Manuals page, click in the section "An Introduction to R ..." on the button [Download pdf]
4. pdf document is displayed
5. hit early on the Back button (I do not know if early on is necessary - but both times I hit it rather early)
6. the previous page shows up; click now the reload button => BANG! CRASH!
Actual Results:  
CRASH!

Expected Results:  
Do not crash.

Adobe Acrobat 7.0.9.50
Your version of Acrobat is no more maintained by Adobe.

Before any further investigation, please upgrade Adobe Acrobat to 8.2 (light) or 9.3.3 (heavy for Windows 2000 PC) :
http://get.adobe.com/fr/reader/
Does this still happen with Firefox 4 and Acrobat X?
Version: unspecified → 4.0 Branch
This bug was reported using a pre-release version of Firefox 4. Now that Firefox 4.0.1 final has been released, can you please update and retest your bug? A fresh profile would be a good starting place to test, 
http://support.mozilla.com/kb/Managing+profiles. If you continue to see the issue, can you please update this bug with your results?

Filter: firefox4prebugsunco
no response from reporter
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Keywords: crash
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.