Closed Bug 383826 Opened 16 years ago Closed 7 years ago

Adobe Reader 8.1 plugin issues alert of "An internal error has occurred", then partially renders pdf files in test case of Bug 368821 Comment #1

Categories

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

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: World, Unassigned)

References

Details

Attachments

(3 files)

This is spin-off of Bug 368821.

Adobe Reader 8.1 plugin partially renders pdf files in test case of Bug 368821 Comment #1 (many iframes with pdf file in it) when internal error occurs(alert of 'internal error' is displayed by plugin).
   testcase: https://bugzilla.mozilla.org/attachment.cgi?id=253469
After this, problem such as Bug 368821 occurs. 

(Scenario and test result)
1. Open url of the test case in a tab.
2. Alert of "An internal error has occurred" is displayed by Acrobat plugin.
   (This alert was not issued when Adobe Reader 8.0.)
3. Not all pdf in iframes are renderd.
  (This was also observed when Adobe Reader 8.0)  
4. Sometimes, error message from server is displayed in a frame.
   Displayed contents depends on error, and is not displayed many times.

(Environment)
A) Property of C:\Program Files\Adobe\Reader 8.0\Reader\Browser\nppdf32.pdf
   Version Info.
     File version : 8.1.0.137
     Detail / file version & product version : 8.1.0.2007051000
B) Adobe Reader's option setting (Environment/Internet)
   C-1) Display PDF in Browser (D) : Checked
   C-2) Allow fast web view (A) : Checked / Unchecked
   C-3) Allow speculative download in the background (S) : Checked / Unchecked
   Partial rendering occurred in any combination of C-2) and C-3).
C) Tested browsers
   Seamonkey 1.1.1, Firefox 2.0.0.4, Firefox trunk nightly(2007/6/04 build). 
   (Above partial rendering of PDF occurred in any browser)

(Note)

Problems after above partial rendering varied by a) test procedure, b) Adobe Reader's "Internet" setting, c) Browser and its version.
 Case-1:
  1) Open a pdf in a tab, 2) Load the testcase in the tab, 3) "Back" button
  => Crashed in many test runs (Bug 368821).
        => Starting of stand alone Adobe Reader doesn't complete in many cases.
           Killing of AcroRd32.exe and restart was required.
     But hang (page rendering doesn't complete) in some test runs.
        => Starting of stand alone Adobe Reader has no problem,
           and open a PDF by Adobe Reader works well.
           But opening of PDF in any browser dispays white window.
           This is true even when browser other than "partial render" occurred.
 Case-2:
  1) Load the testcase in a tab, 2) Open a pdf in new tab, 3) Reload at 1-st tab
  => PDF content is not displayed at 2)/3). (white window or white iframe)
        => Starting of stand alone Adobe Reader has no problem,
           and open a PDF by Adobe Reader works well.
           But opening of PDF in any browser displays white window.
           This is true even when browser other than "partial render" occurred.

It looks that both of problem in plugin side and problem in AcroRd32.exe side are involved, then phenomenon depends on the problem of plugin/AcroRd32.exe.
Summary: Adobe Reader 8.1 plugin partially renders pdf files in test case of Bug 368821 Comment #1 → Adobe Reader 8.1 plugin issues alert of "An internal error has occurred", then partially renders pdf files in test case of Bug 368821 Comment #1
Component: Plug-ins → PDF (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-reader
Version: Trunk → unspecified
wada,

Before the test can complete I get a message from Reader "The maximum number of files are already open. No other files can be opened or printed until some are closed." at the point where all but 23 of the iframes are populated.

I don't get any of the mentioned errors and the 50 iframes that were populated look good.

WFM?
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.