Closed Bug 852510 Opened 7 years ago Closed 2 years ago

crash in LdrShutdownThread with Bandoo's DataMngr/Search Results Toolbar or Hotspot Shield Helper

Categories

(Firefox :: Extension Compatibility, defect, critical)

Product:
Firefox
Component:
Extension Compatibility
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox20 --- affected
firefox21 - affected
firefox22 - affected
firefox23 --- affected
firefox24 --- affected
firefox48 --- affected
firefox49 --- affected
firefox-esr45 --- affected
firefox50 --- affected
firefox51 --- affected
firefox52 --- wontfix

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash)

Crash Data

I'm filing a bug for this long-standing issue not actionable.

It's #47 top browser crasher in 19.0.2, #21 in 20.0b5, #38 in 21.0a2, and #44 in 22.0a1.

It's slightly correlated to an old version of datamngr.dll not blocklistable:
     43% (111/259) vs.   2% (3439/170379) datamngr.dll
          0% (1/259) vs.   0% (1/170379) 
         38% (99/259) vs.   2% (3095/170379) 1.0.0.1
          0% (1/259) vs.   0% (4/170379) 3.0.0.4777
          0% (1/259) vs.   0% (5/170379) 3.0.0.5259
          3% (9/259) vs.   0% (77/170379) 3.0.0.5371
          0% (0/259) vs.   0% (26/170379) 3.0.0.56544

Signature 	LdrShutdownThread More Reports Search
UUID	ac2717fa-6135-4665-8d58-fba1c2130319
Date Processed	2013-03-19 13:10:13
Uptime	1131
Last Crash	18.9 minutes before submission
Install Age	1.5 weeks since version was first installed.
Install Time	2013-03-09 01:17:12
Product	Firefox
Version	19.0.2
Build ID	20130307023931
Release Channel	release
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	x86
Build Architecture Info	GenuineIntel family 6 model 42 stepping 7
Crash Reason	EXCEPTION_ACCESS_VIOLATION_EXEC
Crash Address	0x661732c3
App Notes 	
AdapterVendorID: 0x8086, AdapterDeviceID: 0x0116, AdapterSubsysID: 04d91028, AdapterDriverVersion: 8.15.10.2345
D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ 
Processor Notes 	sp-processor09.phx1.mozilla.com_28902:2008
EMCheckCompatibility	True
Adapter Vendor ID	0x8086
Adapter Device ID	0x0116
Total Virtual Memory	2147352576
Available Virtual Memory	814252032
System Memory Use Percentage	62
Available Page File	4099063808
Available Physical Memory	1174634496

Frame 	Module 	Signature 	Source
0 		@0x661732c3 	
1 	ntdll.dll 	LdrShutdownThread 	
2 	ntdll.dll 	RtlExitUserThread 	
3 	msvcr100.dll 	_endthreadex 	f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:365
4 	msvcr100.dll 	_callthreadstartex 	f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:314
5 	msvcr100.dll 	_threadstartex 	f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:292
6 	kernel32.dll 	BaseThreadInitThunk 	
7 	ntdll.dll 	__RtlUserThreadStart 	
8 	ntdll.dll 	_RtlUserThreadStart 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=LdrShutdownThread
It's #21 browser crasher in 20.0.1, #12 in 21.0b7, #29 in 22.0a2, and #58 in 23.0a1.

It's still correlated to Bandoo's DataMngr and Search Results Toolbar:
    70% (306/436) vs.   1% (1345/136061) mgrldr.dll (Search Results Toolbar)
     67% (293/436) vs.   1% (1216/136061) Datamngr.dll (Search Results Toolbar and DataMngr)
          8% (35/436) vs.   0% (193/136061) 5.0.0.5848
          1% (3/436) vs.   0% (32/136061) 5.0.0.5867
          7% (30/436) vs.   0% (192/136061) 5.0.0.6254
          0% (2/436) vs.   0% (55/136061) 5.0.0.6272
          0% (1/436) vs.   0% (1/136061) 5.0.0.6661
          0% (1/436) vs.   0% (7/136061) 5.0.0.6764
          1% (5/436) vs.   0% (26/136061) 5.0.0.6765
          9% (39/436) vs.   0% (88/136061) 5.0.0.6767
          0% (1/436) vs.   0% (4/136061) 5.0.0.6851
          1% (5/436) vs.   0% (21/136061) 5.0.0.6907
          4% (18/436) vs.   0% (52/136061) 5.0.0.6969
          4% (18/436) vs.   0% (47/136061) 5.0.0.6972
          3% (11/436) vs.   0% (46/136061) 5.0.0.7062
          1% (3/436) vs.   0% (26/136061) 5.0.0.7066
          4% (17/436) vs.   0% (41/136061) 5.0.0.7073
         13% (55/436) vs.   0% (230/136061) 5.0.0.7107
          3% (13/436) vs.   0% (34/136061) 5.0.0.7186
          1% (3/436) vs.   0% (11/136061) 5.0.0.7189
          0% (2/436) vs.   0% (2/136061) 5.0.0.7218
          7% (30/436) vs.   0% (68/136061) 5.0.0.7254
          0% (1/436) vs.   0% (4/136061) 5.0.0.7272

     33% (142/436) vs.   1% (1835/136061) {1FD91A9C-410C-4090-BBCC-55D3450EF433} (DataMngr)
         22% (95/436) vs.   1% (1660/136061) 1.0
          1% (3/436) vs.   0% (23/136061) 5.0.0.6765
          8% (37/436) vs.   0% (112/136061) 5.0.0.6767
          0% (2/436) vs.   0% (7/136061) 5.0.0.6851
          1% (5/436) vs.   0% (19/136061) 5.0.0.6907
     28% (121/436) vs.   0% (602/136061) {C4A4F5A0-4B89-4392-AFAC-D58010E349AF} (DataMngr)
          3% (14/436) vs.   0% (69/136061) 5.0.0.6969
          3% (11/436) vs.   0% (72/136061) 5.0.0.7062
          0% (2/436) vs.   0% (32/136061) 5.0.0.7066
          3% (15/436) vs.   0% (47/136061) 5.0.0.7073
         11% (47/436) vs.   0% (290/136061) 5.0.0.7107
          0% (2/436) vs.   0% (2/136061) 5.0.0.7218
          0% (0/436) vs.   0% (1/136061) 5.0.0.7220
          7% (30/436) vs.   0% (86/136061) 5.0.0.7254
     16% (68/436) vs.   0% (415/136061) {377e5d4d-77e5-476a-8716-7e70a9272da0} (Search-Results Toolbar 1.2.0.0)
     15% (67/436) vs.   1% (1090/136061) afurladvisor@anchorfree.com (Hotspot Shield Helper)
         11% (49/436) vs.   1% (863/136061) 1.0
          4% (18/436) vs.   0% (227/136061) 1.1
      7% (30/436) vs.   0% (104/136061) {C2C2A16E-2E64-478A-992C-82E136577FCD} (DataMngr?)
          4% (17/436) vs.   0% (67/136061) 5.0.0.6972
          3% (13/436) vs.   0% (37/136061) 5.0.0.7186
status-firefox20: --- → affected
status-firefox21: --- → affected
status-firefox22: --- → affected
status-firefox23: --- → affected
tracking-firefox21: --- → ?
Component: General → Extension Compatibility
Keywords: topcrash
Summary: crash in LdrShutdownThread → crash in LdrShutdownThread with Bandoo's DataMngr/Search Results Toolbar or Hotspot Shield Helper
Version: 19 Branch → Trunk
We have done some outreach to contacts at Bandoo as of yesterday, waiting to hear back.
status-firefox24: --- → affected
Bandoo is fixing on their end, so no need to track for a change on ours.
tracking-firefox21: + → -
tracking-firefox22: + → -
(In reply to Alex Keybl [:akeybl] from comment #3)
> Bandoo is fixing on their end
When? It's #15 top crasher in 21.0, #5 in 22.0b6, and #13 in 23.0a2.
Flags: needinfo?(jorge)
I don't think I was involved in this particular conversation, or at least I can't find it in my email archives.

Bhavana?
Flags: needinfo?(jorge) → needinfo?(bbajaj)
I reached out to them for an update yesterday and have heard back. They are going to have rollout a release to fix the issue this week and will keep us posted once done.
Flags: needinfo?(bbajaj)
Micheal from Bandoo recently updated that the fix for this is up as of this morning and so we should be expecting the crash volume to go down in the next few days.
This is only going down very slowly, it's #17 on 22 release right now.
It's now #27 browser crasher in 22.0, #11 in 23.0b10, and #30 in 24.0a2.
This has been going down on all channels for a while, dropped to #38 on 23.0.1, but for now it still hold onto topcrash criteria by being #14 on 24.0b3 - let's watch it for a little bit longer and hope it drops out there as well.
Keywords: topcrash
Crash volume for signature 'LdrShutdownThread':
 - nightly (version 51): 0 crashes from 2016-08-01.
 - aurora  (version 50): 5 crashes from 2016-08-01.
 - beta    (version 49): 72 crashes from 2016-08-02.
 - release (version 48): 88 crashes from 2016-07-25.
 - esr     (version 45): 136 crashes from 2016-05-02.

Crash volume on the last weeks (Week N is from 08-22 to 08-28):
            W. N-1  W. N-2  W. N-3
 - nightly       0       0       0
 - aurora        1       1       0
 - beta         17      17       4
 - release      28      28       7
 - esr           4       8      18

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content   Plugin
 - nightly
 - aurora            #136
 - beta    #413      #1627
 - release #1043               #89
 - esr     #969
status-firefox48: --- → affected
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox-esr45: --- → affected
Crash volume for signature 'LdrShutdownThread':
 - nightly (version 52): 0 crashes from 2016-09-19.
 - aurora  (version 51): 1 crash from 2016-09-19.
 - beta    (version 50): 13 crashes from 2016-09-20.
 - release (version 49): 84 crashes from 2016-09-05.
 - esr     (version 45): 173 crashes from 2016-06-01.

Crash volume on the last weeks (Week N is from 10-03 to 10-09):
            W. N-1  W. N-2
 - nightly       0       0
 - aurora        1       0
 - beta         13       0
 - release      61      23
 - esr          18      20

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content   Plugin
 - nightly
 - aurora            #632
 - beta    #916
 - release #1044     #5403     #129
 - esr     #509                #300
status-firefox51: --- → affected
Crash volume for signature 'LdrShutdownThread':
 - nightly (version 54): 0 crashes from 2017-01-23.
 - aurora  (version 53): 0 crashes from 2017-01-23.
 - beta    (version 52): 11 crashes from 2017-01-23.
 - release (version 51): 48 crashes from 2017-01-16.
 - esr     (version 45): 427 crashes from 2016-08-03.

Crash volume on the last weeks (Week N is from 01-30 to 02-05):
            W. N-1  W. N-2  W. N-3  W. N-4  W. N-5  W. N-6  W. N-7
 - nightly       0
 - aurora        0
 - beta          5
 - release      31       0
 - esr           9      12      19      26       2      23      23

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content   Plugin
 - nightly
 - aurora
 - beta    #2797     #282
 - release #541      #1911     #265
 - esr     #568                #280
status-firefox52: --- → affected
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix
With WebExtensions being the only valid way of doing extensions in Firefox 57, I don't think this bug is still relevant.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.