Closed Bug 116790 Opened 23 years ago Closed 23 years ago

Crash in MOZRMI36.DLL

Categories

(SeaMonkey :: UI Design, defect)

x86
OS/2
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: cowwoc2020, Assigned: paulkchen)

References

()

Details

(Keywords: qawanted)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:0.9.7+) Gecko/20011221 BuildID: 2001122111 Visit the URL and you'll get: 12-24-2001 14:58:02 SYS3175 PID 00b5 TID 0001 Slot 00e5 D:\MOZ\MOZILLA.EXE c0000005 1d646282 P1=00000001 P2=0000c000 P3=XXXXXXXX P4=XXXXXXXX EAX=00d6d000 EBX=0000c000 ECX=00000009 EDX=0000004e ESI=0000006c EDI=00290000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:1d646282 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:0012e66c SSACC=f0f3 SSLIM=ffffffff EBP=0012e6a4 FLG=00212206 MOZRMI36.DLL 0002:00016282 Reproducible: Always Steps to Reproduce: 1. Visit page 2. 3.
Did not crash on Linux (Mozilla 0.9.7, build id 2001122108)
Summary: Crash in MOZRMI36.DLL → Crash in MOZRMI36.DLL
wfm with win2k build 20011224.. OS/2 only ?
WFM, win98SE 2001122208
I have had the mentioned crash, although not on the same web page. Since the build of between 12/06 and 12/08 (I not sure exactly which) all of the daily builds including the .0.9.7 "release build" have been crashing in various DLL modules. Here are three of the latest. I always fall back to the 12/06 nightly which has not had these problems. These are all from the nightly builds of the night before the date on the abend. 12-21-2001 14:11:54 SYS3186 PID 02b4 TID 0001 Slot 014a G:\WARPZILL\BIN\MOZILLA.EXE c000009d 007c9d48 EAX=01a32b30 EBX=009d3437 ECX=01a32878 EDX=01a32b30 ESI=0200bac0 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:007c9d48 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:001317e8 SSACC=f0f3 SSLIM=ffffffff EBP=00131828 FLG=00012286 MOZRMI36.DLL ------------------------------------------------------------ 12-21-2001 15:39:11 SYS3175 PID 02c9 TID 0001 Slot 0164 G:\WARPZILL\BIN\MOZILLA.EXE c0000005 00000001 P1=00000001 P2=00000001 P3=XXXXXXXX P4=XXXXXXXX EAX=013e4761 EBX=00a4507c ECX=013e4848 EDX=013e4500 ESI=00d7ad90 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:00000001 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:001317ec SSACC=f0f3 SSLIM=ffffffff EBP=00131828 FLG=00012202 12-24-2001 11:19:25 SYS3175 PID 04cb TID 0001 Slot 016f G:\WARPZILL\BIN\MOZILLA.EXE c0000005 0d060683 P1=00000001 P2=000000e4 P3=XXXXXXXX P4=XXXXXXXX EAX=0138f890 EBX=0091675c ECX=00000000 EDX=0138f890 ESI=0186b570 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:0d060683 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:00131960 SSACC=f0f3 SSLIM=ffffffff EBP=00131998 FLG=00012206 NKCACHE.DLL 0001:00000683
I can't recreate this on the specified page. MOZRMI36 is the C runtime, so here is no telling what caused this. Do you see this crash on this page consistently?
Yes, the browser dies as soon as it loads up some resource from ad.doubleclick.net .. I doubt it's the actual page which kills it; I think it's the ad itself. But yes, the crash is consistent even now (I tried flushing both memory/disk cache to no avail).
Can you try creating a new profile? I can't recreate it and I am not sure where to go with it. Can you try saving the page locally and seeing if you can recreate it?
Can't reproduce under 2002011017.. Maybe it's been fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
mass-verifying WorksForMe bugs. reopen only if this bug is still a problem with a *recent trunk build*. mail search string for bugspam: AchilleaMillefolium
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.