Closed Bug 140744 Opened 22 years ago Closed 22 years ago

Browser crashed while loading page

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
OS/2
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: dwnoon, Assigned: Matti)

References

(
URL
)

Details

(Keywords: crash) 

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:1.0rc1) Gecko/20020418
BuildID:    2002041811

When I went to read the news from the BBC, the browser crashed before the front
page had loaded. It was the first selection I had made since starting Mozilla.

Reproducible: Sometimes
Steps to Reproduce:
1. Start Mozilla.
2. Select a bookmarked site.
3. Crash!

Actual Results:  
04-28-2002  15:00:20  SYS3176  PID 1351  TID 0001  Slot 006b
E:\MOZILLA\BIN\MOZILLA.EXE
c000001c
1db63704
EAX=01ea4e98  EBX=00000118  ECX=00000000  EDX=012c0000
ESI=00000118  EDI=01ea4fb0
DS=0053  DSACC=d0f3  DSLIM=1fffffff
ES=0053  ESACC=d0f3  ESLIM=1fffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0b43  GSACC=10f3  GSLIM=00003fff
CS:EIP=005b:1db63704  CSACC=d0df  CSLIM=1fffffff
SS:ESP=0053:0013178c  SSACC=d0f3  SSLIM=1fffffff
EBP=001317b8  FLG=00012246

MOZRMI36.DLL 0002:00013704


Expected Results:  Page should display.

Warp 4, fixpack #12.
Connected to the Web via a Squid proxy running on a LINUX box. The requested
page had not yet been cached, though.
wfm, 1.0RC1, Linux
Keywords: crash
wfm using build 2002042803 on Win2k (trunk).
David:
> 2. Select a bookmarked site.

it does happen when you click on a bookmark, right?
is it possible for you to attach your bookmark file?
It is very sporadic. I just did the same sequence of mouse clicks that resulted
in the original crash, and everything worked.

Anyhow, I will e-mail pab@blinkenheights.ch with my bookmark file attached to
the mail message. It is far too large to post here and have Bugzilla send to a
multitude of people.
Tested Davids bookmarks.html... no problem here.. no crash

> It is very sporadic.
..so can you reproduce the 'bug' or not? ...or is the problem 'just', that
mozilla does crash very often?
Did you try to create a new profile?
Start mozilla with:
mozilla -profilemanager
Sometimes mozilla has problems with the config-files from older builds and do
crazy thins..
When I wrote "very sporadic" I meant exactly that: it does not occur very
frequently. The instance that produced the register dump occurred when the
system was under quite a heavy load. It is quite possible that one or more of
Mozilla's threads were starved of CPU cycles.

I think somebody who has the link map for the DLL in question (MOZRMI36.DLL)
should look and see what is supposed to be going on in the area of code that
crashed. This will then give us a better idea of what the real cuase might be.
We can't do anything with the map for MOZRMI36 - it is the C runtime.

Crashes in here can mean anything.
Do you still see these crashes with RC2? 

I can't recreate them at all.
I received the following crash with RC2 when I was editing 
preferences. I clicked on the "Appearance" tab and:

05-15-2002  12:22:43  SYS3175  PID 0034  TID 0001  Slot 
0053
H:\MOZILLA\BIN\MOZILLA.EXE
c0000005
1de50a07
P1=00000001  P2=00000014  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=00000000  EBX=00000014  ECX=00130efc  EDX=00f54e38
ESI=00130efc  EDI=00130efc  
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:1de50a07  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:00130d90  SSACC=f0f3  SSLIM=ffffffff
EBP=00130efc  FLG=00010216

PLDS4.DLL 0001:00000a07

This was before I had applied either of the fixes from the 
IBM FTP server.

After I applied the fixes, I went to my usual news site 
(http://news.bbc.co.uk) and this happened as the front page 
was loading:

05-15-2002  12:27:25  SYS3175  PID 003e  TID 0001  Slot 
0053
H:\MOZILLA\BIN\MOZILLA.EXE
c0000005
1d313e62
P1=00000001  P2=0000018c  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=00f55728  EBX=007e5480  ECX=00000000  EDX=0013008c
ESI=00af2020  EDI=00010004  
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:1d313e62  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:00130030  SSACC=f0f3  SSLIM=ffffffff
EBP=1d4d922c  FLG=00010206

GKHTML.DLL 0001:00003e62

So, there still seems to be something weird going on. Be 
aware that I am running the SMP kernel of eCS 1.0, so there 
could be race conditions among the threads that would not 
appear on a uniprocessor system.
I have just rebooted the system to Warp 4 + FP #12, using the uniprocessor
"Merlin" kernel. Warpzilla has been very stable for the last 5-10 minutes of
active Web surfing, including a visit to the BBC. This is not absolute proof
that the crashes are SMP-related, but it does lead one to wonder.
If you can recreate the crashes still on SMP, can you try marking the EXE as 
MPUNSAFE and see if that fixes it?

Thanks
I have not suffered any crashes since the two I posted in my previous message.
Those both occurred within minutes of installing RC2 and then the 2 fixes.

In the [almost] 3 days since then this baby has been bullet-proof, even using
the SMP "Aurora" kernel.

One thing I haven't tried is changing the skin. I normally switch from Classic
to Modern as part of my initial configuration. I might try switching and see if
this indices some instability. If it does, I will "execmode" the program so that
all threads are dispatched on the same CPU.
I'm going to mark this WORKSFORME based on the last comments.

If you run into more crashes, please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.