Closed
Bug 83546
Opened 23 years ago
Closed 23 years ago
back button after viewing quicktime page crashes
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: abrobston, Assigned: serhunt)
References
()
Details
(Keywords: crash)
Attachments
(1 file)
365.87 KB,
text/plain
|
Details |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010527 BuildID: 2001052708 After viewing a link with MIME type image/png with Quicktime 5.0.1 plug-in, using the back button causes a crash. Reproducible: Always Steps to Reproduce: 1. Make sure you have QuickTime 5.0.1 and it is set as the viewer for PNG image files. 2. Go to above URL (a bug report), and select the first attachment (a screenshot of that bug). 3. Once the page with the screenshot has loaded, use the back button to go back to the bug report. Actual Results: Mozilla loads and displays the bug report page, then crashes. Expected Results: Mozilla should have loaded and displayed the bug report page, then not crashed. I am unclear how to get the Talkback ID, but I can give the you Dr. Watson log. Crash was in module KERNEL32.DLL. I will attach the log shortly.
Reporter | ||
Comment 1•23 years ago
|
||
OK, apparently Bugzilla isn't going to let me attach that Watson log. Watson won't let me copy the stack trace either. I'll figure out something.
Comment 2•23 years ago
|
||
We need either a talkback id from the crash or the stacktrace...otherwise we cant do much with this bug. Thanks in advance.
Keywords: crash,
stackneeded
Reporter | ||
Comment 3•23 years ago
|
||
Talkback ID is TB31691441Q. However, it may not be a valid (or helpful) ID, because it is user-initiated (after the crash and before pressing "Close" on the resulting dialog). I cannot seem to get Talkback to recognize the crash automatically. If you do need a stack trace in addition to that Talkback data, what does that include from the Dr. Watson log? The entire "Details" section from Watson is very long.
Keywords: quicktime
Comment 4•23 years ago
|
||
Without knowing its probably easist to attach the whole log. That would be helpful.
I cannot reproduce this with my two days old debug build in NT. Shrirang can you?
Reporter | ||
Comment 6•23 years ago
|
||
Comment 7•23 years ago
|
||
nope..i tried all attachments a number of times..no crash. on 0613 trunk windows NT. Andrew, is this reproducible for you every time? I even tried a few png images but no crash..
Reporter | ||
Comment 8•23 years ago
|
||
I can reproduce this bug every time in 2001-06-13 on Windows 98. I just attached the Diagnosis and Details sections of the Watson log, which includes the stack trace.
Keywords: stackneeded
Comment 9•23 years ago
|
||
Confirming reproducable on 2001061504 / Windows 98 / Quicktime 5.0.1 - Backing out of a page with elements that use the Quicktime 5 plugin (in my case, *.mov and *.png) crashes mozilla
Assignee | ||
Comment 10•23 years ago
|
||
Hm... Win98 specific? Peter, Shriarng, do you have debug environment set on 98?
Reporter | ||
Comment 11•23 years ago
|
||
Just for kicks, would someone like to mark this bug "new?"
Comment 12•23 years ago
|
||
Andrew or Mark: could you try to reproduce this crash with a latest nightly build with talkback enabled? Please be sure to fill out the "email" section of the crash report with your bugzilla e-mail or include the TB ID#. So, if I understand, to reproduce I should go to this attachment and hit "Back": http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36343 Andrei, I too can not reproduce (on Windows 2000, debug build). Shrirang, can you?
Comment 13•23 years ago
|
||
no crash on my NT..no matter what :(
Comment 14•23 years ago
|
||
Tested on Win 98 with 6_14_09_trunk and 6_15_06_trunk builds. With Quicktime 5 installed, could not reproduce the bug. WORKSFORME.
Comment 15•23 years ago
|
||
Thanks Chris. Marking so.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•