Closed
Bug 457157
Opened 16 years ago
Closed 16 years ago
tab crash after destroying an embedded pdf object (Adobe Reader 9.0.0)
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 434593
People
(Reporter: clark, Unassigned)
References
Details
Attachments
(1 file)
2.12 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.2) Gecko/2008091620 Firefox/3.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080925033548 Minefield/3.1b1pre
We are creating an embedded pdf, printing it without user action, then destroying it. The print takes place just fine, but apparently it's the something in destroying the pdf object that is the problem. This problem did not exist in version 2. It crashes 3.0.1 completely, and in 3.0.2 and the above build, it's only the tab that "crashes".
Reproducible: Always
Steps to Reproduce:
1.create an embedded pdf object
2.print it without user intervention
3.destroy the pdf object
Actual Results:
The printing takes place perfectly. The page looks totally normal and the cursor is flashing where it should be. But upon the next action, nothing happens, ie, the page was apparently already frozen. Closing the tab and reopening is adequate to continue the application.
Expected Results:
The page should have remained active and the tab should not have required closing.
The website that demonstrates it is behind a log-in which I can supply if needed. Thanks for the help!!
Updated to reflect that the version is 3
Version: unspecified → 3.0 Branch
Comment 2•16 years ago
|
||
Please go to about:crashes and include the crash reports for this issue here. I'd lay some odds that you are not using the correct allocator/deallocator for the runtime.
Glad to, Dave. Here it is. Thanks.
Signature @0x780040
UUID 92dc2a91-8eb4-11dd-a764-001321b13766
Time 2008-09-29 22:56:06-07
Uptime 409
Product Firefox
Version 3.0.3
Build ID 2008092417
OS Windows NT
OS Version 5.1.2600 Service Pack 3
CPU x86
CPU Info GenuineIntel family 6 model 9 stepping 5
Crash Reason EXCEPTION_ILLEGAL_INSTRUCTION
Crash Address 0x780040
Comments Bugzilla #457157
Comment 4•16 years ago
|
||
So yeah it is a crash triggered by nppdf32.dll it seems. Is that your plugin?
Comment 6•16 years ago
|
||
Then I'd suggest running in a debug build and getting a more detailed stack to see exactly where it is crashing in your code.
Two updates: replication and a stack trace.
Short of being able to cook up a debug build, we've written a dedicated page to replicate the problem. It's not behind any log-in. It's http://biblionix.com/firefox_pdf/
The stack trace from a crash is attached.
Does this help?? Thanks.
This is a stack trace for a crash.
Also, a crash report was submitted that referenced this bug number.
err, by YOUR plug-in, we mean did you, your employer or your organization write and compile / build your own pdf plug-in?
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Program Files\Adobe\Reader 9.0\Reader\browser\nppdf32.dll -
seems to indicate you didn't, unless you work for adobe
msinto'm travelling, please redirect to the pdf team
Assignee: nobody → msintov
Component: Extension Compatibility → Plug-ins
Product: Firefox → Core
QA Contact: extension.compatibility → plugins
Version: 3.0 Branch → 1.9.0 Branch
Updated•16 years ago
|
Assignee: msintov → nobody
Comment 10•16 years ago
|
||
(In reply to comment #3)
> Signature @0x780040
> bp-92dc2a91-8eb4-11dd-a764-001321b13766
Adobe Reader's modules;
> Module|AcroRd32.dll|9.0.0.332|AcroRd32.pdb|(snip)
> Module|nppdf32.dll|9.0.0.332|Nppdf32.pdb|(snip)
Adding "Adobe Reader 9.0.0" in bug summary.
Summary: tab crash after destroying an embedded pdf object → tab crash after destroying an embedded pdf object (Adobe Reader 9.0.0)
Comment 11•16 years ago
|
||
Bug 453787 is report of similar problem with Adobe PDF-Plugin 8.1.0.137.
Setting Dependency. Please remove dependency if it's wrong.
Depends on: 453787
Reporter | ||
Comment 12•16 years ago
|
||
Sorry for the delay. You are correct - we did not write our own plug-in.
Comment 13•16 years ago
|
||
Duplicate; anything with the window proc and embedded PDFs and DOM changes are the same (Adobe plug-in bug). No known workaround, and I can't say when I'm allowed to release a fix.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•