330184 - Acrobat Reader blocked by Firewall -> Seamonkey hangs up

Status: RESOLVED WORKSFORME

(Plugins Graveyard :: PDF (Adobe), defect)

Description

[Martin Haake]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

i clicked on a pfd-link an my firewall asked "Application starts other Application: Seamonkey starts Acrobat Reader. Do you allow that?"

Since expected the link would go to a html and did not want to read a pdf, I answered "no".

Than Seamonkey hang up so had to shoot the process.

Reproducible: Always

Steps to Reproduce:
use a firewall that whatches application starting e.g. Kerio Personal Firewall

Click on a pdf link and do not allow Acrobat Reader to be startet by Seamonkey

Comment 1

[Andrew Schultz]

Do you have Acrobat installed as a plugin or as an external app?

Comment 2

[Martin Haake]

i installed Acrobat Reader 7.0 for some old Mozilla. It told that is can act as plugin, too. I confirmed.

Now i have copied the plugin folder of my old mozilla (i think it was 1.7.8) for SeaMonkey to use.

Comment 3

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)
> did not want to read a pdf, I answered "no".
> Then Seamonkey hang up so had to shoot the process.

This was easily be recreated with Seamonkey 2006040309-trunk/Win-2K and Adobe Reader 7.0.5 and Kerio Personal Firewall.

Who is wrong?
KPF who simply intercepts and discards request of starting Acrord32.exe and never returns feed back to requester?
Adobe plugin who waits for starting of Acrord32.exe forever and never pass control back to Seamonkey?
Seamonkey who can not handle Adobe plugin's forever wait and becomes freeze?
Or Seamonkey who waits for starting of Acrord32.exe forever then freezes?

No response from Acrord32.exe is similar situation when hang/freeze in Acrord32.exe. And hang/freeze in Acrord32.exe causes Mozilla's freeze. And cancel of hanging Acrord32.exe from task manager can resolve freeze of Mozilla in many cases.
But no such workaround when this bug's case...
(See dependency tree of meta Bug 336184 for hang/freeze when Adobe Reader 7.0.x)

Comment 4

[Andrew Schultz]

If the plugin doesn't return control on its own, there's nothing we can do without something like bug 156493.  Can someone report this to Adobe so they can fix this (since that actually has a chance of happening).

Comment 5

[WADA:World Anti-bad-Duping Agency]

I've found a very simple and perfect workaround, which was/is (and probably will be) always effective solution when Adobe's PDF plugin problem:
  - Disable "Display PDF in Broweser" option of Adobe Reader.

Comment 6

[WADA:World Anti-bad-Duping Agency]

Confirming, based on my re-creation test result in comment #3.

Comment 7

[Wayne Mery (:wsmwk)]

Martin Haake, wada can you still reproduce?

(In reply to comment #4)
> If the plugin doesn't return control on its own, there's nothing we can do
> without something like bug 156493.  Can someone report this to Adobe so they
> can fix this (since that actually has a chance of happening).

This was fixed with the release of Firefox 3.6.4.

Comment 8

[Martin Haake]

I don't know, since I have a new Computer and installed Firefox. I keep my Firefox and the Adobe Plugin up to date. I have no problems anymore.

Comment 9

[Wayne Mery (:wsmwk)]

wada, ratty, would SM still be afflicted by this plugin issue? (does it have OOP for adobe PDF?)

Comment 10

[Philip Chee]

We use the same backend code for OOP plugins with the same blacklists as Firefox, so if it is fixed for Firefox 4.0b12 then it's fixed for SeaMonkey 2.1b2.

Comment 11

[Wayne Mery (:wsmwk)]

Thanks ratty. so, WFM per Martin