Closed Bug 274437 Opened 20 years ago Closed 20 years ago

mozilla crashed while changing proxy settings, now can't start it anymore

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 242393

People

(Reporter: io, Unassigned)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) 
Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) 
Gecko/20040910

Mozilla crashed while changing proxy settings (which I've been always doing 
without any problem), and now crashes each time I try to launch the browser!
Version is 1.7.3 (Win XP Pro SP2)
Talkback IDs are:
TB2519509E (crash during proxy settings change)
TB2519520X (crash trying to launch mozilla after the previous crash)
TB2519898X (same as baove)

Is there a way to restart my Mozilla without having to re-install it?
nsHttpChannel::OnDataAvailable 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/netwerk/protocol/http/src/nsHttpChannel.cpp,
line 3630]
nsInputStreamPump::OnStateTransfer 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsInputStreamPump.cpp,
line 436]
nsInputStreamPump::OnInputStreamReady 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsInputStreamPump.cpp,
line 337]
nsInputStreamReadyEvent::EventHandler 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/io/nsStreamUtils.cpp,
line 215]
PL_HandleEvent 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 674]
PL_ProcessPendingEvents 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 612]
_md_EventReceiverProc 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 1415]
USER32.dll + 0x30494 (0x77d40494)
USER32.dll + 0x30494 (0x77d40494)
_setargv()
kernel32.dll + 0x16d4f (0x7c816d4f)
kernel32.dll + 0x399f3 (0x7c8399f3)

According to bug 242393, this is now fixed on the branch builds.

*** This bug has been marked as a duplicate of 242393 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Keywords: crash
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.