Closed Bug 219987 Opened 21 years ago Closed 18 years ago

All pdfs freeze mozilla when trying to open using Acrobat 6.0

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 214137

People

(Reporter: timothyv, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6

I have recently installed Adobe Acrobat 6.0 Professional and since then Mozilla
will freeze (takes up 99% CPU usage and a butt-load of system memory) when
trying to open the files.  Have replicated with the latest version and same
problem.  Am able to open same documents with Acrobat 6.0 in IE, so doesn't
appear to be a general problem with opening Acrobat via a browser.

Reproducible: Always

Steps to Reproduce:
1. Install Acrobat 6.0 Professional
2. Go to any website (try http://socrates.berkeley.edu/~ivrylab/pubs.html)
3. Try opening the .pdf

Actual Results:  
Mozilla freezes and eventual refuses to respond (crashed my computer once)

Expected Results:  
Opened the file.
QA Contact: asa
I have also experienced this issue, with Acrobat 6.0 Professional and Firebird 0.6.1

I have not yet had it crash my computer, but I have always had to shut down the
non-responsive Firebird through the Task Manager. With Internet Explorer, this
difficulty does not occur, thus leading me to conclude that it is an issue with
Acrobat and Firebird.

My current workaround (when I am able to do so) is to save the PDF to my hard
drive and then open it manually with Acrobat.
I can confirm this problem in FB 0.7+ (Mozilla/5.0 (Windows; U; Windows NT 5.0;
en-US; rv:1.6b) Gecko/20031125 Firebird/0.7+) - build 11/28/2003. It freezes on
each PDF document, just on the different stages. Sometimes it happens right
after I click a link, sometimes after browser starts to load document (blank
window), sometimes after loading document when I try to scroll it.
have the same problem
I have this problem as well.  Mozilla 1.5 through 1.6B and Acrobat 6 has gave me
the problem.  My workaround is using right click to save to my hard drive as
well.  When I load the pdf in the browser, it will work for a minute, but will
always lock mozilla up until I use the task manager to kill the mozilla process.
 I haven't had any problems with mozilla locking up my computer.
I'm using today's build (v1.7a Build ID: 2004012209) in Windows XP, and I've
been getting similar effects for a long time (can't remember when I first
noticed it.

However, Mozilla does not crash, and the problem is not while loading PDF files.
They load fine (CPU usage does go skyward, but Mozilla is still responsive). The
problem is when leaving a PDF file (closing the tab it's in, going Back, or
exiting Mozilla). On leaving a PDF file, Mozilla pauses for several seconds, and
becomes unresponsive. But, after five or six seconds, the Mozilla software
redraws itself and is back in my control.

This is not really a problem for me, but it seems worth mentioning here.
I can't confirm this bug. it may be a slow connection, lack of memory or acrobat
configuration itself. cheers.
This is exactly what has happened with me.  It started with 1.5 and now 1.6.  I
had Acrobat 5.0 full with no problems, now Acrobat 6.0 full with problems. 
WinXP SP1 w/all patches.

Rob
I've seen it too.  If I kill the Firefox process, a modal dialog put up by
Acrobat remains.  ('PDFs are open in other browser windows; if you exit the
Reader, they'll close too' or something like that, on closing the PDF window.  I
think I had to kill firefox and click past some other annoying modal notice to
get that far...
Status: UNCONFIRMED → NEW
Ever confirmed: true
I was able to replicate this bug on Windows XP Professional with both Firebird
0.7 and the newest Firefox update.

This bug does not seem to be a NEW bug because there have been numerous
replicants, and on many different system coonfigurations and browsers. This bug
is not RESOLVED either, as some of the other reports claim, because it keeps
appearing in the newest versions of Mozilla browsers since as far back as May of
2003.

Om my system configuration, Firefox becomes unresponsive and crashes when
clicking return and waiting before choosing an option from the dialog box that
appears and asks whether or not to close Acrobat. Once the option box 'never
show this dialog box again' is checked, the error stops occuring. I believe this
is why the bug has not been fixed. Once this is done, the bug never appears again.
Can people still reproduce this with Acrobat Reader 6.0.1?
QA Contact: aebrahim
I had no problem at all using Firefox 0.8 final clean install running with Adobe
Reader 6.0.1.
Unless people can reproduce this with Acrobat 6.0.1 and a recent Firefox build,
I'm going to mark this as WORKSFORME in a few days.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040311
Firefox/0.8.0+
Acrobat 6.0.1

I Am seeing this with German version of Acrobat and a clean Firefox install.
(In reply to comment #14)
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040311
> Firefox/0.8.0+
> Acrobat 6.0.1
> 
> I Am seeing this with German version of Acrobat and a clean Firefox install.

Please make sure that:

1) Adobe was not opened for the first time (which leads to ask if You agree with
the license use and sometimes blocks everything)

2) Check Adobe reader auto update feature is disabled

I think It will be useful if You can try with a 0.8 final zip edition using the
profile already installed to see if You can reproduce the bug. Thanks a lot.
I confirm that on my system, running Firefox 0.8 on XP with all latest patches
and Acrobat 6.0.0 Professional, the browser loads the PDFs just fine but when
you try to leave/close the PDF page FireFox appears to use 99% of the CPU (task
manager) and hangs in that state for several seconds. If you wait long enough it
finally does succeed and redraws the previous page and the CPU falls down to
normal. Very annoying !

The PDF opened directly with Acrobat or from within IE do not trigger the same
behaviour.

Thank you for any consideration of this bug.

Robert Alexander - Rome - Italy
I think we should make clear if this bug refers to Adobe *reader* or Adobe
Acrobat (the PDF file producer), anyway I think this is more Adobe related than
Firefox related.....
Dear Alessandro,
I think we could close this bug:

We where talking about Adobe Acrobat 6.0 Professional (the PDF producer as you
call it).

The problem for me has been FIXED by upgrading the original release (6.0.0) with
the 6.0.1 update (11 March 2003 or 3 Nov 2003 - I hate American dates 8->).

Any PDF URL is now opened as fast as previously but hitting the back button
immediately gives me back the control to the browser.

Take care.
Bob Alexander
(In reply to comment #18)
> I think we could close this bug:

We'd better wait some day for Soeren Unruh (comment #14) reply :-)
I must have missed the "Professional" part in the description.

My comment applied to "Adobe Reader 6.0.1" with license agrreed on and
autoupdate disabled (removed plugin), and also verified with 0.8 final.

I'm therefore fine with closing this bug, as the comment doesn't apply.
(In reply to comment #20)
> I must have missed the "Professional" part in the description.
> 

Soeren hello.

Just to share this for the future:

The READER is NOT called Acrobat (see www.adobe.com
http://www.adobe.com/products/acrobat/main.html ): it's proper name is Adobe Reader.

Adobe ACROBAT (Pro or not Pro) is the programs which MAKES the PDFs.

Of course this is a very common mistake we all do when speaking relaxed 8->

Take care. Bob
So I was seeing this problem on a laptop that came pre-installed with Acrobat
Reader 5. I'd subsequently loaded Adobe Acrobat 6 Professional, upon which all
PDF's I tried to view in Firefox choked the browser.

On a whim, I opened up regedit, and discovered that there were still Acrobat
Reader 5 registry keys laying around under the HKEY_LOCAL_MACHINE and
HKEY_CURRENT_USER hives, under Software\Adobe. I removed all of these keys
relating to v5 and restarted, then tested with Firefox.

Sure enough, I could now view PDF's with Firefox without any problems...!
Hopefully this will help some people. Is this at all a Firefox bug that it's
using the v5 plugin when v6 is installed? I never uninstalled Acrobat Reader v5,
but noticed that when I try to launch the executable for v5, v6 actually
launches... Maybe Firefox needs to somehow give priority to the v6 plugin, if it
is found?

NOTE: This problem was STILL OCCURING with v6.0.1, so that is not the solution
(at least for me).
The same on FF 0.8, Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) 
Gecko/20040206 Firefox/0.8.
Always have to kill FF task to get back to browsing. It affects all running 
copies of the program.
I have not had this problem for some time except for the early days of the
Firebird. However, recentrly nightlies started to have this problem.

This time, there is not problem in opening PDF files, but if you push "forward",
"backward" button or "tab closing" button ( The tab contains the PDF file. ),
then the Firefox freezes.
This problem existed before but there was no this problem for sometime.
But recent builds started to have this problem again.

For me, pdf files are opened well, but when I try to close it by closing
its enclosing tabs or closing the Firefox window, it makes the Mozilla hangs.

Plug-in version is 6.00.
(In reply to comment #25)
> This problem existed before but there was no this problem for sometime.
> But recent builds started to have this problem again.
> 
> For me, pdf files are opened well, but when I try to close it by closing
> its enclosing tabs or closing the Firefox window, it makes the Mozilla hangs.
> 
> Plug-in version is 6.00.

Please update to the 6.01 version and retest.
reassign to new default assignee.

fwiw this wfm fine using acrobat 6.0.1 professional on winxp
Assignee: firefox → bugs
Flags: blocking1.0?
I have been having this same problem on Windows for the last several Mozilla
builds since 1.4 RC1 (beta, RC and released versions) and for both Acroread and
Acrobat professional at versions 5 and 6 on both Win2k and WinXP.

The instant that a PDF is selected for viewing in Mozilla, things are still OK.
 Within seconds of the Acrobat or Acroread process showing up, Mozilla consumes
CPU to such an extent that all other Normal or less processes are starved.  This
causes the Acrobat process to take a very very long time to do anything.

As a temporary workaround, I go into task manager and set Mozilla to "Below
Normal" scheduling.  At that point, Acrobat can continue loading it's plugins
and doing it's init.  Linux users might be able to renice Mozilla to allow
acrobat to finish initialization.

Once Acrobat is ready to begin displaying the PDF, Mozilla stops consuming high
CPU and I can set it back to normal.

If Acrobat is running already, then this does not occur.

This seems to imply that Mozilla is in a loop waiting for some sort of response
from the acrobat plugin and that response is only given when the acrobat program
is fully started.

I have the same problem in Internet Explorer 6 SP1 on both 2k and XP, which
seems to imply it may be related to the acrobat plugin, or maybe there is a
common calling method between the browsers.

The problem is worse when acroread is loading pieces of a PDF rather than the
whole PDF.  While it's waiting for network, Mozilla hangs; however, I'm not sure
if it is still Mozilla consuming CPU at that point because I try to avoid split
PDFs.

Everything is fine if a PDF is shell launched.

This seems to be a duplicate bug.  The bugs I see which seem to match this are:<BR>
<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=198954">198954</a><BR>
<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=219987">219987</a><BR>

Updated to Acroread 6.0.1 and problem still exists.

Acroread only hung about 15 seconds this time, and loaded fewer of it's own
plugins on init; however, it was recently installed and run, so it was likely
fully cached.

After closing acroread, copying large files to overwrite cache, and restarting,
the hang condition was still very short, indicating that the adobe code has
optimized it's initialization procedure severely.

So what it seems is that if a plugin takes more than a couple of seconds to
start, the Mozilla's CPU hog condition will cause that plugin to become CPU
starved, and Mozilla's CPU hog condition seems to be because the plugin hasn't
finished loading yet.

Again, I see the same situation with IE6; however, For all I know, IE6 uses
mozilla-like code to call plugins.

A good test would be to see if there are other plugins that take a long time to
initialize and if so, do they do the same thing to Mozilla?   Why is Mozilla
spinning it's wheels?  Is it effectively calling an I/O routine in the plugin
that blocks the main thread while it waits for response?

I know I used to have problems with Mozilla hanging on web/html accesses when I
would have network hangs, but I don't recall having that happen recently and
don't know if that is related or not.

I'm sorry I don't have the tools or experience to isolate this to plugin calling
methods versus plugin itself.

The problem might simply be explained away with a policy of "plugins should
start in 5 seconds or less to prevent browser hangs", or maybe someone still
wants to look further into it.  Either way, it doesn't presently seem to be a
serious problem when using Acro 6.0.1.

Current env:
Thinkpad T21, Pentium III 800, 512MB PC133, S3 Graphics Savage/IX 1014
Microsoft Windows 2000 5.00.2195 Service Pack 4 C4EB 4.0 (OPK B2195 SP4)
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421
Adobe Reader 6.0 Version 6.0.1 11/3/2003, AGM Version 4.10.50, CoolType version
4.13.42, Core Version 6.1, JP2K Version 1.0.22891, ADM Version 3.01x1
investigate. 
Flags: blocking1.0? → blocking1.0+
Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040502
Firefox/0.8.0+
and: Adobe Reader 6.0.0 05/19/2003

Trying to load a PDF into a new tab _in the background_.

Everything stalls while Reader loads -- piggy piggy piggy.  However, loading
Reader executable from the taskbar happens immediately.  The load SHOULD be on a
separate thread so it doesn't hang everything up.  
So, I go and make lunch and come back.  The PDF tab has the URL on the tab-label
but it is just blank white.
(In reply to comment #31)
> Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040502
> Firefox/0.8.0+
> and: Adobe Reader 6.0.0 05/19/2003

WHY don't You read previous comments?!?!?
The PDF file can be opened under Firefox 0.8 however, the browser freezed after
the pdf file been opened on Acrobat 6.0. (CPU goes to 100% and firefox became
unresponsive).
I had been seeing this bug for a while now, including 20040523 on Win2k. But I
then reinstalled Acrobat Reader 6.0.1 and it's been fine since :-/. 

Previously, I had manually moved all the /plug-ins/ files to /Optional/ in order
to speed load times and, of course, the reinstallation process put all those
files back in the original /plug-ins/ directory -- perhaps moving those files
caused this problem?

(The moving-the-plugins technique:
http://dotnetjunkies.com/WebLog/darrell.norton/archive/2003/10/06/2095.aspx)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040523
Firefox/0.8.0+
Adobe Reader 6.0.1 11/03/2003

Was good with the nightly around Comment#32 time - 2004-05-08;
Now it is bad again.

Note, for me this behavior is particularly noticable when I'm loading the Reader
(plug-in) into a background tab.  [I don't see that factor included above FWIW]
*** Bug 245143 has been marked as a duplicate of this bug. ***
I'm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a)
Gecko/20040519 Firefox/0.8.0+ on WinXP home with all patches and I also have
this problem.  It does also occur for me when the acrobat reader is NOT loaded
in the background.  
I get this problem too with Acrobat 6.0 proffessional Trial, even if I choose to
quit at the trial screen (it comes up before Acrobats loads and tells you how
much time you have left to try the software).

Really, acrobat and acrobat reader support is scary (it makes me cringe when I
see the Acrobat or Acrobat Reader splash screen - I'm sure you don't want users
cringing when they use your product) in all versions of Mozilla, and is
something that really should be corrected before the next big release of either
Mozilla or Firefox.
Component: Download Manager → Plug-ins
Product: Firefox → Browser
Version: unspecified → Trunk
Assignee: bugs → nobody
QA Contact: aebrahim → core.plugins
*** Bug 247952 has been marked as a duplicate of this bug. ***
*** Bug 247067 has been marked as a duplicate of this bug. ***
If Acrobat Reader is opened, this doesn't happen, for example:

1. Start Mozilla on W32.
2. Navigate to a page with a link to a pdf file
3. open the pdf file withint Mozilla
4. start Adobe Acrobat Reader (you don't need to open any document in it) and
leave it in memory
5. press the back arrow in Mozilla, and it will go to the previous page immediately.

Now close Acrobat Reader and Mozilla. Make sure no other copies of Mozilla or
acrobat are in memory (task list). Repeat steps 1, 2, 3 (skip step 4) and when
you click to the back arrow it will take anywhere from 30 to 60 seconds to show.

If your problem is "complete freeze" due to Adobe Reader 6.0, this is DUP of Bug
214137 and is already resolved by Adobe Reader 6.0.1 or later.
See also Bug 212067.

If your problem is "terrible slowness of Adobe Reader 6.0.x (x=0,1,2)", see Bug
194986 Comment #4 and read the plugindoc document.
> http://plugindoc.mozdev.org/faqs/acroread.html#win-ar6-speed also
describes how to escape from terrible slowness of Adobe Reader 6.0.
*** Bug 222708 has been marked as a duplicate of this bug. ***
Not a "blocker"
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
*** Bug 277804 has been marked as a duplicate of this bug. ***
*** Bug 222835 has been marked as a duplicate of this bug. ***
*** Bug 280338 has been marked as a duplicate of this bug. ***
*** Bug 281059 has been marked as a duplicate of this bug. ***
Isnt this a dupe of bug 173061?
I can confirm this behaviour for at least FireFox 1.0.1 and 1.0.3 (and possibly
others), running on Windows XP Professional SP2. It appears that all of the
FireFox windows are 'waiting' and/or 'blocking' until a plugin is (fully)
started, causing all FireFox windows to become unresponsive during that period.
One the plug-in is started, all FireFox windows resume to normal behaviour and
become responsive again.

Adobe Acrobat Reader 6 is indeed a good example of this behaviour, but so is
Sun's Java Plug-in. I can confirm this with at least Sun Java Plug-in 1.5.0_02
(but possibly others as well).

*** Bug 305406 has been marked as a duplicate of this bug. ***
To bug opener and all "mee too" comment posters:

Bug 204017(Crash) Bug 212067(Crash) and Bug 214137(Hang) are already closed as WORKSFORME, since problem of Adobe Acrobat Reader 6.0(.0) was already resolved by 6.0.1. 
Why this bug is still open? Are you all still experiencing problem even after 6.0.1?
I don't experience any hang since 7.0, but don't know what about 6.0.1
(In reply to comment #54)
> I don't experience any hang since 7.0
Péter Pallos, thanks for reponding. Please be carefull when upgrade to 7.0.x, because many crash or hang are reported for 7.0.x, although number of bugs for 7.0.x is currently smaller than number of still-kept-open bugs for 6.0(.0).
See dependency tree of meta Bug 336184 and Bug 336184 comment #2.    
No response except from Péter Pallos.
Closing as DUP of Bug 214137.

If similar hang will occur on Adobe Acrobat/Reader 7.0.x, see dependency tree of meta Bug 336184, and read all bugs related to Adobe Acrobat/Reader 7.0.x in the tree before open new bug, please.

*** This bug has been marked as a duplicate of 214137 ***
No longer blocks: 336184
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.