511330 - Firefox 3.5.2 Crashes 100% of the Time when using an Anonymous Proxy Client

Status: RESOLVED INVALID

(Core :: Networking, defect)

Description

[nbokil]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2

Firefox 3.5.1 worked fine when using the anonymous proxy client Anonymizer.  However, when upgrading to 3.5.2, Firefox now crashes 100% of time when Anonymizer is running.  Firefox 3.5.2 works fine when Anonymizer is shut down, but this is problematic.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to Firefox 3.5.2
2. Start Anonymizer
3. Start Firefox.
Actual Results:  
Firefox crashes 100% of the time when the above, basic steps are followed.

Expected Results:  
Firefox crashed.

Firefox 3.5.2 should run fine--just like 3.5.1 did--when Anonymizer is used.

Comment 1

[Matthias Versen [:Matti]]

>2. Start Anonymizer

Failed at this step.
What is the Anonymizer ?

And please follow https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[crispinroad]

Still occurring. 3.5.2 is the culprit, earlier versions are fine. I have to delete FF, then reinstall an early version.

My codes :
bbefe0f5-f3fd-4e7e-b600-3212e2090817	18/08/2009	00:11
b0db82df-1caf-4485-8038-9ac6d2090817	18/08/2009	00:11
da68bce2-e934-4dbd-ad26-2a18b2090809	09/08/2009	23:08
e86248dd-5947-4634-9bd3-aac0d2090806	06/08/2009	23:32
173b38d1-24fa-4c53-8fec-a737c2090806	06/08/2009	23:31
04ebc32c-5152-4a8a-ae87-fba672090806


Anonymizer can be found at www.anonymizer.com/

Comment 3

[Matthias Versen [:Matti]]

0  	 	@0x17d1c8  	
1 	xul.dll 	nsSocketTransport::OnSocketEvent 	netwerk/base/src/nsSocketTransport2.cpp:1447
2 	xul.dll 	nsSocketEvent::Run 	netwerk/base/src/nsSocketTransport2.cpp:98
3 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:510
4 	xul.dll 	NS_ProcessPendingEvents_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:180
5 	xul.dll 	nsSocketTransportService::Run 	netwerk/base/src/nsSocketTransportService2.cpp:575
6 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:510
7 	nspr4.dll 	PR_DestroyLock 	



0  	 	@0x17d550  	
1 	xul.dll 	nsNSSComponentConstructor 	security/manager/ssl/src/nsNSSModule.cpp:184
2 	xul.dll 	nsGenericFactory::CreateInstance 	obj-firefox/xpcom/build/nsGenericFactory.cpp:80
3 	xul.dll 	nsComponentManagerImpl::CreateInstanceByContractID 	xpcom/components/nsComponentManager.cpp:1687
4 	xul.dll 	nsComponentManagerImpl::GetServiceByContractID 	xpcom/components/nsComponentManager.cpp:2253
5 	xul.dll 	CallGetService 	obj-firefox/xpcom/build/nsComponentManagerUtils.cpp:94
6 	xul.dll 	nsCOMPtr_base::assign_from_gs_contractid 	obj-firefox/xpcom/build/nsCOMPtr.cpp:132
7 	xul.dll 	nsCOMPtr<nsISupports>::nsCOMPtr<nsISupports> 	obj-firefox/dist/include/xpcom/nsCOMPtr.h:940
8 	xul.dll 	EnsureNSSInitialized 	security/manager/ssl/src/nsNSSComponent.cpp:321
9 	xul.dll 	nsCryptoHashConstructor 	security/manager/ssl/src/nsNSSModule.cpp:214
10 	xul.dll 	xul.dll@0x89dde7 	
11 	xul.dll 	xul.dll@0x89dde7

from the modules list:
AnonTCP.dll  	6.6.1.0
Could it be that the frame0 crash point is in their dll ?


Did you contacted http://www.anonymizer.com/ about the issue ?

Comment 4

[timeless]

typically hex addresses are either unloaded modules or dead objects, unloaded modules can identified by running the process under a debugger:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

after it crashes, lm will list the unloaded modules and the log will have other traces hinting about it.

In this case, I don't think it's the right explanation, but a log would help me rule that out.

Comment 5

[nbokil]

I contacted Anonymizer Support and received a response back that there is a known conflict with Anonymizer and Firefox 3.5.2.  Anonymizer reports (on their website) that Anonymizer does not support either Firefox 3 or Internet Explorer 8, which I find unbelievable.  They are working on a compatible service that will support the latest versions of Firefox in Windows Vista and XP and are targeting a release date by the end of 2009, but this has not yet been confirmed.  For those who have an active Anonymizer service, you can request to have your Anonymous Surfing subscription placed in pending status until a compatible service has been released.

Comment 6

[timeless]

wontfix is for issues in our codebase. as this seems to be their fault, for our accounting purposes, we use invalid, this isn't a reflection on you, just blame between us and them.