User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 I was using Mozilla in a website called Business Source Premier. I opened a PDF file, and it opened up OK with the plugin inside the browser. However, whenever I click on back or close the window tab Acrobat will freeze. Mozilla doesnt freeze. It keeps on working, but if I try to open another acrobat file it will freeze. And I need to close the application from the NT Task Manger. Multiple instances of AcroRd32.exe running on the background. Reproducible: Always Steps to Reproduce: 1.Open Mozilla, click on a PDF file. 2.PDF opens OK in window. Click back to go back to previous screen. 3.do a Control+ALT+Del and check the Processes. AcroRD32 will be running. 4.Click on the same PDF file link. 5.Mozilla will freeze. 6.Check the Processes again, there will be 2 instances of AcroRd32.exe. Actual Results: I had to force the application to shut down. Expected Results: close the current AcroRd32.exe and open it up again when needed. I was using the feature when mozilla stays resident in memory. The little icon the taskbar.

I can confirm this - I'd prepared the following problem statement when I thought to search for AcroRd32 and found this one which seems to mirror my problem fairly closely. ================== I just noticed something with Fireird 0.6 (2003-06-07 Mozilla Firebird/0.6) Mozilla 1.4b (2003-05-11) Adobe Acrobat reader 6.0 Trying to read the PDF file http://www.sco.com/scosource/ExhibitC.qxd.pdf (part of the SCO-IMB-Linux exhibits) it seems to take for ever for the PDF file to become readable with Firebird. The first page comes up ok, but trying to get to the second or following takes "forever" Do the same thing with IE-6 the response time is really quite decent. Trying again with Mozilla 1.4 b - same pattern: first page comes up reasonably quickly then stalls trying to get to second page. Watching what's happening with TaskManager (showing Processes, sorted by VM-size with Peak Mem usage, Mem usage, VM Size and CPU% also visible) makes it clear what's happening. With IE-6, loading the above page causes AcroRd32.exe to start, rapidly grab a bunch of memory and burn a lot of cycles, first page shows quickly, clicking next page is virtually instantaneous. Do the same thing with EITHER Firebird or Mozilla 1.4b (one at a time and with AcroRd32.exe not initially running) starts the same, displays the first page much more slowly than did IE6 and when page-forward is clicked stalls and never completes. Killing the process tree for which ever browser is being tested terminates the browser and the AcroRd32 task and everything thereafter is hunky-dory. Regards ... Alec

crash or freeze, can still see this with 1.4 rc2 and acrobat 6

To "Assigned To:" person. Aren't both bug 212067 and bug 214137 DUPE of this bug?

maybe.....the root cause of these bugs needs to be investigated. Does Acrobat 5 work ok? Does the Reader vs. Full product work okay? Have you tried clearning you cache or creating a new profile? Have you tried clearing the "Background download" option in Acrobat? Have you tried a log (NSPR_LOG_MODULES=all:5, NSPR_LOG_FILE=c:\log.txt)? Have you tried on other PDFs, both remote and local? Is this a regression? Does it happen in 1.0, 1.3?

I think this bug can be closed as WORKFORME or FIXED since Adobe 6.0.1 is now available. Bug 212067 and Bug 214137 reports that Adobe Reader 6.0.1 upgrade has resolved hang/crash problems. After upgrade to Adobe Reader 6.0.1, AcroRd32.exe task was still created on browsing pdf in browser window(not external Adobe Reader 6.x) while stand alone Adobe Reader 6.01(Adobe Reader task) does not exist. This task seems to be a stand alone Adobe Reader 6 with no window to support PDF browsing in Browser Window and this is design of Adobe Reader 6. (1) When stand alone Adobe Reaer 6.02 does not exist (1-1) Open PDF in tab - Sprash screen of Adobe Reader was displayed - Acrord32.exe appeared (1-2) Close tab PDF opend - Acrord32.exe still remained (1-3) Open PDF in tab again - Sprash screen of Adobe Reader was not displayed - Acrord32.exe still remained (1-4) Start stand alone Adobe Reader - "Adobe Reader" task appeared - Acrord32.exe task disappeared (1-5) Try to terminate stand alone Adobe Reader - Warning of "PDF opened by browser will be closed" was issued (1-6) Force stand alone Adobe Reader termination - PDF data in tab was cleared - Warning of "PDF in opened by browser will be closed" - "Adobe Reader" task disappeared (2) When stand alone Adobe Reaer 6.02 exist ("Adobe Reader" task exists) (2-1) Open PDF in tab - Sprash screen of Adobe Reader was not displayed - Acrord32.exe did not appear, already started "Adobe Reader" only After this, result is same as (1-5),(1-6) Problem in Acrrord32.exe task kicked by browser seems to be fixed also by Adobe Reader 6.0.1 upgrade. Reporter and commenters, does the problem still occur after upgrade to Adobe Reader 6.0.1 or Adobe Acrobat 6.0.1?

Correction of typo. Sorry for spam. 6.0.2 -> 6.0.1

Just for info, when attempting to download Adobe Acrobat Reader 6.01 for MS-Windows 98SE today, I found that Adobe was instead providing Adobe Acrobat Reader 5.05 vice 6.01. Whether this is their permanent intent I of course don't know, but 5.05 does not crash in the manner being reported for 6.00, after brief testing, which is certainly one way to fix the problem. xanthian@well.com

This WFM using Acrobat 6.0.1. Everything points to this being an Acrobat 6.0.0 bug that was fixed in 6.0.1. Unless somebody can reproduce this on a current build using Acrobat 6.0.1, I am going to close this in four weeks.

I installed 6.0.1, and it worked with 1.5 and 1.6, then stopped working a few days later (maybe a week). Then I de-selected all the Adobe Internet preferences, and it worked again. Then, a few days or a week later all of a sudden it stopped working again. Using Moz 1.6, Adobe Acrobat 6.0 full version on WinXP SP1 all patches. Thought it was just my PC, then experienced problem on another with Adobe Reader 6.0 recently installed and Netscape 7.1 today. Hmph. I can of course right-click and save. But the users are not smart enough. Rob

Comment #9: You're in the wrong bug. Please test with the latest nightly and file a new bug if you still see the problem with Adobe Reader 6.0.1. -> WFM per my previous comment. Feel free to reopen if you still see this behavior on a current nightly using the latest version of Adobe Reader.

*** Bug 276394 has been marked as a duplicate of this bug. ***

*** Bug 325472 has been marked as a duplicate of this bug. ***