Closed Bug 326408 Opened 19 years ago Closed 18 years ago

all Adobe Products Bug after Acrobat reader failer(Firefox hang/freeze/almost 100% CPU/crash after closing PDF)

Categories

(Firefox :: File Handling, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bonnet.pierre, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

Adobe photoshop works well at same time as firefox, until a pdf document has been closed in firefox. 

when a pdf document is oppened in firefox, all Photoshop functions are blocked, but firefox still work.
When I try to close firefox's page containing pdf file then Firefox will start using almost 100% of cpu being blocked. I have to stop firefox in windows task manager. then everything comes back to normal.  


Reproducible: Always

Steps to Reproduce:
1.open firefox
2.open photoshop
3.open a pdf file from link in google sor exemple
4.try to open doc in photoshop - does not work.
5. close pdf file firefox page --> firefox should crash and use 100% OF CPU
6. try to open photoshop ducument --> function don't work
7. stop firefox in windows task manager
8. things work again 

Actual Results:  
1.open firefox
2.open photoshop
3.open a pdf file from link in google sor exemple
4.try to open doc in photoshop - does not work.
5. close pdf file firefox page --> firefox should crash and use 100% OF CPU
6. try to open photoshop ducument --> function don't work
7. stop firefox in windows task manager
8. things work again
(In reply to comment #0)
(A)
> when a pdf document is oppened in firefox, all Photoshop functions are blocked,
> but firefox still work.
> When I try to close firefox's page containing pdf file then Firefox will start
> using almost 100% of cpu being blocked. I have to stop firefox in windows task
> manager. then everything comes back to normal.  

What is Adobe Reader and PDF plugin version? (Read Bug 336184 comment #2)
See dependency tree of meta Bug 336184, if 6.0.x or 7.0.x.

Changing summary for ease of search, and put Bug 336184 in "blocks:" field. 

(B)
> when a pdf document is oppened in firefox, all Photoshop functions are blocked,
but firefox still work.
(C)
> Adobe photoshop works well at same time as firefox, until a pdf document has
> been closed in firefox. 

Cause of hang/freeze/100% CPU of Firefox is hang of Acrord32.exe (hidden/windowless process when kicked thru plugin) after clsing PDF of Tab, and cancel of hanging Acrord32.exe from Task Manager can relief Firefox's freeze in many cases, although not always.
(B) sounds that something wrong in Acrord32.exe when Acrord32.exe is kicked by PDF plugin, and (C) sounds that closing PDF in browser(i.e clsing PDF thru PDF plugin) make it worse, even when it doesn't cause hang/freeze of Firefox(probably forever wait of PDF plugin).

(Q1) 
What will happen if windowless Acrord32.exe process is killed when (B) or (C) occurs?
(Q2) 
Workaround described in Bug 336184 comment #2, (3), B), is effective?
(Adobe Reader's options other than "Display PDF in Browser" looks for me to affect (B). So I suspect that root cause of problem is situation of (B).)
 
Anyway, ask to Adobe for Photoshop's problem, please.
Blocks: 336184
Summary: all Adobe Products Bug after Acrobat reader failer → all Adobe Products Bug after Acrobat reader failer(Firefox hang/freeze/almost 100% CPU/crash after closing PDF)
(In reply to comment #0)
> Actual Results:  
(snip)
> 5. close pdf file firefox page --> firefox should crash and use 100% OF CPU
(snip)
> 7. stop firefox in windows task manager

Firefox process still remained even after "Crash"? Did you reply "Cancel" for dialog by Dr Watoson to terminate crashed Firefox completely? CPU 100% even after the "Crash"?
What is Talkback ID of the crash?
No response for more than one year from bug opener.
Closing as WORKSFORME.

No longer blocks: 336184
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.