Crash in XPCOM.DLL [@MyEventType::destroyMyEvent]

VERIFIED WORKSFORME

Status

()

Core
XPCOM
--
critical
VERIFIED WORKSFORME
17 years ago
16 years ago

People

(Reporter: David W Noon, Assigned: mkaply)

Tracking

({crash})

Trunk
x86
OS/2
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, URL)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031114

Warpzilla died with a GPF in XPCOM.DLL.

Reproducible: Didn't try
Steps to Reproduce:
1. Brought up a Web page.
2. Scrolled with vertical scroll bar with page still loading.
3. Splat!

Actual Results:
03-13-2002  12:18:21  SYS3175  PID 007e  TID 0001  Slot 0071
E:\MOZILLA\BIN\MOZILLA.EXE
c0000005
1dea95e0
P1=00000001  P2=0000001c  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=01df1080  EBX=01e04020  ECX=00000000  EDX=01e05820
ESI=012cd228  EDI=0000003b  
DS=0053  DSACC=d0f3  DSLIM=1fffffff  
ES=0053  ESACC=d0f3  ESLIM=1fffffff  
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0b5b  GSACC=10f3  GSLIM=00003fff
CS:EIP=005b:1dea95e0  CSACC=d0df  CSLIM=1fffffff
SS:ESP=0053:00131980  SSACC=d0f3  SSLIM=1fffffff
EBP=001319e8  FLG=00012202

XPCOM.DLL 0001:000495e0


Expected Results:  'Zilla should have just scrolled down the screen.

OS/2 Warp 4, fixpack #12

This also seemed to corrupt some preference files in the Mozilla subdirectory
tree. This resulted in me reporting bug #130569. I think this dump is the real
cause of that other problem.

I'll try it again after I have backed up my disks.

Updated

17 years ago
Severity: normal → critical
Keywords: crash
(Assignee)

Comment 1

17 years ago
MAP file indicates crash is in

MyEventType::destroyMyEvent in nsTimerImpl, so this is a timer crash.

The only thing that could cause this is if event was null.

Any ideas pav?

Comment 2

17 years ago
->mkaply@us.ibm.com
Assignee: trudelle → mkaply
Component: XP Apps → XPCOM

Updated

17 years ago
Summary: Crash in XPCOM.DLL → Crash in XPCOM.DLL [@MyEventType::destroyMyEvent]

Updated

17 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Comment 3

16 years ago
Do you still see this on current builds?
(Reporter)

Comment 4

16 years ago
I downloaded the 2002/04/14 nightly build yesterday (15 
April) and installed it straight away. I have not seen a 
recurrence of this bug.

To confound the issue of timing, I am now running Warpzilla 
on a much faster machine. The original bug was reported 
when run on a  450 MHz AMD K6-III with 384MiB of RAM. I am 
now running a twin-engined AMD Athlon MP 1600+ system with 
512MiB of RAM. Even though the SMP version of eComStation 
seems only to operate one CPU, it is still 4 or 5 times 
faster than the old machine, while the network interface to 
my cable modem is still running at the same speed.
(Assignee)

Comment 5

16 years ago
I'm marking this as working for now.

If you see it again, please reopen.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME

Comment 6

16 years ago
v 
Status: RESOLVED → VERIFIED
Crash Signature: [@MyEventType::destroyMyEvent]
You need to log in before you can comment on or make changes to this bug.