162480 - The browser crashes :( obiviusly microsoft is trying to stop Mozilla again.

Status: RESOLVED DUPLICATE of bug 141366

(SeaMonkey :: General, defect)

Description

[John McCann]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1b) Gecko/20020721
BuildID:    2002072104

M$ is trying to stop mozilla users getting into their windows update website
again when view the website mozilla crashes and parts of mozilla fail to close
properly requiring the user to restart the machine to use mozilla again.

Reproducible: Always
Steps to Reproduce:
1. Go to the site.
2. Watch mozzila crash and burn.


Actual Results:  Crash and burn.

Expected Results:  View M$ updates avaible to download.

M$ is evil and I had to update IE to version 6 to update windows :/

Comment 1

[R.K.Aa.]

WFM, day old CVS, Linux.

Comment 2

[Olivier Cahagne]

wfm using build 2002081209 on Win2k (trunk).
John, did you get a Talkback window popup when crashing ? If so, please post
Talkback ID here by running 'mozilla/bin/components/talkback.exe'.

Comment 3

[John McCann]

Hmm well me last post hasn't shown up but talkback was not invoked. The data
from the error window is as follows.

MOZILLA caused a divide error in module <unknown> at 0000:00000204.
Registers:
EAX=a4700000 CS=003b EIP=00000204 EFLGS=00000097
EBX=00010001 SS=20e7 ESP=00000fd0 EBP=00007680
ECX=00000001 DS=202f ESI=cc73f000 FS=4bc7
EDX=00000000 ES=450f EDI=cca722a0 GS=2dcf
Bytes at CS:EIP:
cd 30 cd 30 cd 30 cd 30 cd 30 cd 30 cd 30 cd 30 
Stack dump:
003b0204 3ef00006 0246031f 2dcf7680 0000005b 00320000 00f302b5 117f1697 01ff1797
00000204 0000003b 00000217 00000000 00000000 00000000 00000000 

The Error does not occur in mozzila 1.1alpha(2002061104) ( I just downgraded )so
maybe M$ ain't to blame for this one. 

Comment 4

[Mats Palmgren (inactive)]

Please search for duplicates before posting bug reports. There are four crashes
reported on that URL before yours.

*** This bug has been marked as a duplicate of 141366 ***

Comment 5

[Mats Palmgren (inactive)]

BTW, it's a bug in the nVidia driver. Acoording to bug 128961 comment 185 there
is a new driver released that fixes the problem.