Crash in CComApartment::InitRemoting

RESOLVED WORKSFORME

Status

--
critical
RESOLVED WORKSFORME
2 years ago
a year ago

People

(Reporter: wsmwk, Unassigned)

Tracking

({crash})

53 Branch
x86
Windows 7
crash

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

2 years ago
#59 crash for TB 45.8.0. All Win7.

This bug was filed from the Socorro interface and is 
report bp-29960a10-6580-4b02-9550-aae232170326.
=============================================================
0 	ole32.dll	CComApartment::InitRemoting()	
1 	ole32.dll	CComApartment::StartServer()	
2 	ole32.dll	ole32.dll@0x13e6ed	
3 	ole32.dll	CoReleaseMarshalData	
4 	networkitemfactory.dll	CNetworkItem::~CNetworkItem()	
5 	networkitemfactory.dll	CNetworkItem::`scalar deleting destructor'(unsigned int)	
6 	networkitemfactory.dll	CNetworkItem::Release()	
7 	networkitemfactory.dll	IDToNetworkItemRecord::~IDToNetworkItemRecord()	
8 	networkitemfactory.dll	IDToNetworkItemRecord::`scalar deleting destructor'(unsigned int)	
9 	networkitemfactory.dll	IDToNetworkItemRecord::AddRefRecord(int)	
10 	networkitemfactory.dll	LKRhash::CTypedHashTable<CNameToNetworkItemHashTable, IDToNetworkItemRecord const, unsigned short const*, LKRhash::CLKRHashTable>::_AddRefRecord(void const*, int)	
11 	networkitemfactory.dll	LKRhash::CLKRLinearHashTable::_Clear(bool)	
12 	networkitemfactory.dll	LKRhash::CLKRHashTable::Clear()	
13 	networkitemfactory.dll	CNetworkItemFactory::~CNetworkItemFactory()	
14 	networkitemfactory.dll	CNetworkItemFactory::`scalar deleting destructor'(unsigned int)	
15 	networkitemfactory.dll	DelayUnloadHandler(void*, unsigned char)	

Might be gone in 52.0. So far no crashes after 50.0b3 bp-8f1aa3f5-b7f7-4fc0-9399-2d0a82170113
(Reporter)

Updated

2 years ago
See Also: → bug 835319
(Reporter)

Comment 1

a year ago
Crash signature still does not exist in 52.
Also closed bug 835319
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
(Reporter)

Updated

a year ago
Whiteboard: [closeme 2017-06-01]
You need to log in before you can comment on or make changes to this bug.