360576 - calling Adobe Acrobat 6.0 to display a .pdf link causes hang

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[Chris Holst]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; en) Opera 8.50
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5

Acrobat splash screen appears, then all Seamonkey windows report as "not responding" in task manager.  

Reproducible: Always

Steps to Reproduce:
1. Install Acrobat 6.0 as your pdf viewer
2. Click on a pdf link
3. Hang!

Actual Results:  
Hung!

Expected Results:  
Displayed the pdf document.

Comment 1

[Adam Guthrie]

Hang != crash. Also, you should consider using a newer version of Acrobat Reader. Version 6 doesn't play nicely with Mozilla.

Comment 2

[Kent Paul Dolan]

Attachment: Locations of Adobe Plugin DLLs

The 4 copies of this DLL in "c:\ExternCopy\..."
are strays. The other 12 were littered about
the disk by Adobe/Mozilla plugin installation
software. Is all this redundancy necessary?
It is possible (though not all that likely)
that confusion from all these copies somehow
contributes to the failures seen.

This search window snapshot is meant to accompany
the "reply" I'm currently writing to bug 360576.

xanthian.
Kent Paul Dolan, [e-mail]

Comment 3

[Kent Paul Dolan]

(In reply to comment #1)

> Hang != crash. Also, you should consider using a newer version of Acrobat
> Reader. Version 6 doesn't play nicely with Mozilla.

Version 8 isn't infallibly better.

The file here:

http://www.mammoet.com/plaatjes/db/PDFs/3.pdf

opens OK in Acrobat 6.0 or Acrobat 8.0,
if downloaded and opened directly from
the file by Acrobat, but fails to load
(tab stops all processing)
when brought up as a link by SeaMonkey
1.5a, build 2006121709, both with the
6.0.x.xxx and with the 8.0.0.456 version of
the Acrobat plugin nppdf32.dll installed in
c:\Program Files\mozilla.org\SeaMonkey\plugins

Environment: MS-Windows XP "Media Center" 64bit
version, HP Pavilion dv5000 with AMD Turion64
processor.

This is not a general failure, many other
PDF files open fine in either setup.

There's no way to guess if this is a Mozilla
or an Adobe problem, of course.

It is worth mentioning that I found an
astonishing _12_ valid copies, plus 4 more
copies in a backup directory, of this DLL on
my computer with Microsoft's "search" tool.

I've created an attachment with a snapshot
of the search window showing this situation.

I'm assuming this is the same bug as described
by the original reporter. That may not be the
case, but it seemed more maintainer-friendly
to report it this way and let you folks sort
things out, since I have this dandy test case
whose URL I provided.

[I upgraded my Acrobat release in the midst of
trying to solve this problem for myself, that's
why I know the failure is common to the 6.0 and
8.0 releases of Acrobat.]

I'm not sure what the original reporter's situation
was, but my only recovery from this failure was
to kill SeaMonkey with the Microsoft task manager.

xanthian.
Kent Paul Dolan, [e-mail].

Comment 4

[Wayne Mery (:wsmwk)]

do you see this using current version?

Comment 5

[Wayne Mery (:wsmwk)]

WFM with current versions, but => incomplete without info from reporter
please reopen if more information becomes available per previous comments