Closed Bug 350198 Opened 18 years ago Closed 18 years ago

Browser locks, CPU 100% when closing a tab containing Acrobat PDF(Adobe Acrobat 6.0.0)

Categories

(Core Graveyard :: Plug-ins, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 214137

People

(Reporter: liam, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

When I open a PDF in a new tab, then close that tab, the CPU goes to 100% and Firefox stops responding. If multiple PDF tabs are open, the problem only occurs on closing the LAST tab.

Reproducible: Always

Steps to Reproduce:
1.Open a PDF document in Firefox
2.Close the tab/Firefox
3.CPU goes to 100%, Firefox hangs

Actual Results:  
Firefox hangs

Expected Results:  
Tab/Firefox should gracefully close

Adobe Acrobat v6.0.0.878. I know it's old, but I'm not at liberty to upgrade it, and besides this seems like a general error that might crop up elsewhere.

Once Firefox is killed, the screen confirming that I should close Adobe appears, telling me an app is still using it. Perhaps this is not showing in the first instance? I recall this was the bahaviour. However, the 100% CPU issue seems wrong.
Blocks: 336184
Component: File Handling → Plug-ins
Product: Firefox → Core
QA Contact: file.handling → plugins
Version: unspecified → 1.8 Branch
(In reply to comment #0)
> Adobe Acrobat v6.0.0.878.
DUP of old Bug 214137. See meta Bug 336184 and see dependency tree of it.

*** This bug has been marked as a duplicate of 214137 ***
No longer blocks: 336184
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Summary: Browser locks, CPU 100% when closing a tab containing Acrobat PDF → Browser locks, CPU 100% when closing a tab containing Acrobat PDF(Adobe Acrobat 6.0.0)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.