345904 - Crash immediately after upgrading to latest nightly build [@ PL_DHashTableOperate]

Status: RESOLVED DUPLICATE of bug 342646

(Core :: Security: PSM, defect)

Description

[Jackie Liu]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060725 BonEcho/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060725 BonEcho/2.0b1

I downloaded the latest nightly build today and have upgraded to it (installed over existing).  Then, when the actual installing part ends and the setup goes to the final screen, "Open Bon Echo Now" (something along the lines of that) is checked.  So I click finish, a Onecare Firewall Notification comes up, I click Stop Blocking This Program (or something along the lines of that) (this is probably unrelated), and Firefox opens.  Then it crashed...and Talkback came up.

Reproducible: Always




Talkback ID: TB21416208K

Comment 1

[Dave Townsend [:mossop]]

This stack appears to be the same as the ad muncher bug, but the reporter is using Microsoft OneCare Firewall.

Comment 2

[Adam Guthrie]

Incident ID: 21416208
Stack Signature	PL_DHashTableOperate 4a62299c
Product ID	Firefox2
Build ID	2006072504
Trigger Time	2006-07-25 13:28:57.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	xpcom_core.dll + (0000131e)
URL visited	
User Comments	I just downloaded and ran the installer for the latest nightly build (July 25th), and ended the installed with the Start Bon Echo checkbox checked. When Firefox started, it crashed, opening Talkback.
Since Last Crash	10 sec
Total Uptime	10 sec
Trigger Reason	Access violation
Source File, Line No.	c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/build/pldhash.c, line 547
Stack Trace 	
PL_DHashTableOperate  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/build/pldhash.c, line 547]
nsCStringHashSetSuper::GetEntry  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/ds/nsHashSets.cpp, line 43]
nsSSLIOLayerAddToSocket  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp, line 2574]
nsSSLIOLayerNewSocket  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp, line 1410]
nsSSLSocketProvider::NewSocket  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsSSLSocketProvider.cpp, line 72]
nsSocketTransport::BuildSocket  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 988]
nsSocketTransport::InitiateSocket  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1090]
nsSocketTransport::OnSocketEvent  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1406]
0xf18b0c24
nsComboboxControlFrame::FireValueChangeEvent  [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/layout/forms/nsComboboxControlFrame.cpp, line 2491]
0x15fff44d

Comment 3

[Adam Guthrie]

Jackie, I know you mentioned something about a Microsoft firewall, but are you running Ad Muncher as well?

Comment 4

[Steve England [:stevee]]

I asked this in IRC but he said no, he wasn't running admuncher.

Comment 5

[Jackie Liu]

I think it's ok with today's nightly (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060726 BonEcho/2.0b1).  If no one objects to this, this seems to be fixed.

Comment 6

[Jackie Liu]

It seems to be happening again in today's latest nightly (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060727 BonEcho/2.0b1).  However, this time, the Firefox window doesn't open at all and no Talkback is launched.  There's just a customary "firefox.exe needs to close" (something along the lines of that).

Comment 7

[Jackie Liu]

This seems to be fine again (bug does not occur) in today's nightly "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060729 BonEcho/2.0b1".  Can anyone confirm?

Comment 8

[Steve England [:stevee]]

Do we know what specific bug fixed this? If not, then WORKSFORME or INVALID.

Comment 9

[Kai Engert [:KaiE:]]

Steve, this was fixed with bug 342646, this one could actually be made a dupe.

Comment 10

[Jackie Liu]

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