Closed Bug 79942 Opened 24 years ago Closed 21 years ago

browser crash on Package_Tag test on netlanski

Categories

(Core Graveyard :: Plug-ins, defect, P1)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: shrir, Assigned: peterl-bugs)

References

()

Details

(Keywords: crash, Whiteboard: [PL:VENDOR][THIS IS A SHOCKWAVE BUG, NOT A MOZILLA BUG])

win 0509. GPF-plugin.dll,iml32.dll Steps to recreate: 1. Launched browser and went to page: http://poppy.macromedia.com/netlanski/ 2. Under BrowserDependencies, Click Package_Tag 3. Shockwave frame loads, then pauses and Gpf's again this might be a dup of 77572. but filing as a seperate issue.
Confirming. But the stack points to a shockwave DLL.
all the crashers about macromedia are pointing to iml32.dll or dirapi.dll. Nothing else is spitteed out in the trace. :(. I am just filing these as seperate issues for the time being.
Are they always at the same address? Compare the talkback reports and be sure it's the same versin of shockwave.
i just compared that the addresses are different for each crash and the shockwave version is the same all the time
*** This bug has been marked as a duplicate of 77572 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
well, this still does crash...on 0522 trunk on windows.
Status: RESOLVED → VERIFIED
i should reopen...(marked verif by mistake) stack trace is the same : Call Stack: (Signature = IML32.dll + 0x6bba3 (0x6906bba3) feb7a88f) IML32.dll + 0x6bba3 (0x6906bba3) 0xd8573205
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Status: REOPENED → ASSIGNED
Keywords: crash, qawanted
Target Milestone: --- → mozilla1.0
Does this still crash?
yes 0724 branch win , still crashes
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
this still crashes just like it did a year ago..
adding whiteboard keywords
Priority: -- → P1
Whiteboard: [ADT2][PL RTM]
mass move PL RTM
Whiteboard: [ADT2][PL RTM] → [ADT2 RTM][PL RTM]
this is an esoteric crash inside Shockwave's plugin --->moving to future
Keywords: qawanted
Whiteboard: [ADT2 RTM][PL RTM]
Target Milestone: mozilla1.0.1 → Future
Severity: critical → normal
verify the crash, I will attach the stack in a bit
Whiteboard: [PL2:NA]
Target Milestone: Future → mozilla1.0.2
adding nsbeta1+
Keywords: nsbeta1+
Target Milestone: mozilla1.0.2 → mozilla1.2alpha
Target Milestone: mozilla1.2alpha → mozilla1.3alpha
this is a vendor issue
Assignee: peterlubczynski → beppe
Status: ASSIGNED → NEW
Keywords: nsbeta1+
Whiteboard: [PL2:NA] → [PL:VENDOR][THIS IS A SHOCKWAVE BUG, NOT A MOZILLA BUG]
Target Milestone: mozilla1.3alpha → Future
reassign
Assignee: beppe → peterl
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
not a bug in Mozilla? Invalid.
Status: NEW → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.