Closed Bug 318611 Opened 19 years ago Closed 16 years ago

Once the pdf file is open, clicking "back" locks up the browser with 100% CPU usage and only way out is to control/alt/delete.

Categories

(Core Graveyard :: Plug-ins, defect)

1.8 Branch
x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jameshamers, Unassigned)

References

()

Details

(Keywords: hang)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Open the pdf file
clicking "back" arrow in menu bar locks up the browser 
100% CPU usage
Only way out is to use control/alt/delete.

Reproducible: Always

Steps to Reproduce:
1. click to pdf file
2. click the green back arrow on menu bar

Actual Results:  
screen goes "white" in color
Loss of keyboard control
Menu bar does not appear
Control Alt Delete showed 100% CPU usage

Expected Results:  
gone to the previous page in the browser
Related to bug 266698 or maybe Core bug 219987 comment 6?
Severity: normal → critical
Component: General → Plug-ins
Keywords: hang
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → 1.8 Branch
(Q1) What is the version of Adobe Reader (or Adobe Acrobat Reader)?
     Please note that plugin's version number is 7.0.0
     even for newest Adobe Reader 7.0.5.
(Q2) Is killing of windowless AcroRd32.exe process from "Task Mangaer" 
     (Not started from start menu or shortcut. Stared by PDF open in browser.) 
     a effective recovery procedure from "CPU 100%" of Firefox?
(Q3) Does freeze occur in your environment when Tab, where PDF is opened,
     is closed instead of "Back"?
     See Bug 318733 for freeze when TAb close/Adobe Reader 7.0.x.
No response from bug opener for more than two years...
Closing as INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.