Closed Bug 184471 Opened 22 years ago Closed 21 years ago

browser and mail crash randomly with voodoo3 2000 card

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: markhnj, Assigned: asa)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130

When using either the browser or mail client the program will crash.  It can
happen at any url with no specific pattern/behavior that I can discern.  This
will occur with annoying frequency when I use a 3dfx Voodoo3 2000 video card. 
Without changing any other components in my system, if I install an ATI Rage XL
card all seems well.  No other programs on my system, including browsers and
mail clients, have a problem with the Voodoo card.  So I assume Mozilla doesn't
like the Voodoo card or it's driver.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
are you running latest video driver version ?
Can you post Talkback ID for this crash "mozilla/bin/components/talkback.exe"
Severity: normal → critical
Keywords: crash, stackwanted
Yes running latest version of video drivers. See these tb's for more info
TB1484770H
TB14817389Q
TB14846310H

Also Mozilla crashed with ATI card, TB14903381K, but it is far less buggy with
ATI card.
Whiteboard: TB14817389Q
Blocks: 185584
No longer blocks: 185584
Sorry, the only stack I could retrieve was 

TB14903381K
KERNEL32.DLL + 0x62cea (0xbffd2cea) 
mark, does it still happen using latest nightly build ?
http://ftp.mozilla.org/pub/mozilla/nightly/latest
Whiteboard: TB14817389Q
resolving due to lack of response from reporter

please reopen if you can reproduce this bug with a recent Mozilla build.

WFM with voodoo3 2000 on WinXP
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Keywords: stackwanted
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.