Closed Bug 629634 Opened 15 years ago Closed 14 years ago

Crash [@ ffplugin.dll@0x19d0c4 ][@ _purecall | ffplugin.dll@0x19d0c8 ][@ ffplugin.dll@0x19caa4 ][@ ffplugin.dll@0x19cf04 ][@ ffplugin.dll@0x173ee4 ][@ ffplugin.dll@0x174524 ][@ ffplugin.dll@0x175244 ][@ ffplugin.dll@0x173ed4 ] with Bandoo 5.0 or 6.0

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
blocking2.0 --- .x+
status1.9.2 --- wanted

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, topcrash, Whiteboard: [softblocker][fixed by Bandoo extension 5.1])

Crash Data

It is a residual crash signature that exists in 3.6 and the trunk. With combined signature, it is #8 top crasher in 4.0b10. I guess it is a Bandoo bug and not a Javacript one. Signature FFPlugin.dll@0x19d0c4 UUID 84612a98-ed7b-4aa4-a4af-da55b2110127 Time 2011-01-27 22:02:13.721380 Uptime 8049 Last Crash 49259 seconds (13.7 hours) before submission Install Age 97714 seconds (1.1 days) since version was first installed. Product Firefox Version 4.0b10 Build ID 20110121161358 Branch 2.0 OS Windows NT OS Version 5.1.2600 Service Pack 3 CPU x86 CPU Info GenuineIntel family 6 model 15 stepping 13 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x9 App Notes AdapterVendorID: 8086, AdapterDeviceID: 2772, AdapterDriverVersion: 6.14.10.4906 Frame Module Signature [Expand] Source 0 FFPlugin.dll FFPlugin.dll@0x19d0c4 1 xul.dll NS_InvokeByIndex_P xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:102 2 xul.dll XPC_WN_CallMethod js/src/xpconnect/src/xpcwrappednativejsops.cpp:1593 3 mozjs.dll CallCompiler::generateNativeStub js/src/methodjit/MonoIC.cpp:666 4 mozjs.dll js::mjit::ic::NativeCall js/src/methodjit/MonoIC.cpp:873 5 @0x1e2adb5d 6 mozjs.dll js::mjit::EnterMethodJIT js/src/methodjit/MethodJIT.cpp:748 7 mozjs.dll CheckStackAndEnterMethodJIT js/src/methodjit/MethodJIT.cpp:774 8 mozjs.dll js::mjit::JaegerShot js/src/methodjit/MethodJIT.cpp:791 9 mozjs.dll js::RunScript js/src/jsinterp.cpp:654 10 mozjs.dll js::Invoke js/src/jsinterp.cpp:737 11 mozjs.dll js::ExternalInvoke js/src/jsinterp.cpp:858 12 mozjs.dll js::JSProxyHandler::call js/src/jsproxy.cpp:248 13 mozjs.dll JSCrossCompartmentWrapper::call js/src/jswrapper.cpp:601 14 mozjs.dll js::JSProxy::call js/src/jsproxy.cpp:810 15 mozjs.dll js::proxy_Call js/src/jsproxy.cpp:1062 16 mozjs.dll js::Invoke js/src/jsinterp.cpp:693 17 mozjs.dll js::ExternalInvoke js/src/jsinterp.cpp:858 18 mozjs.dll JS_CallFunctionValue js/src/jsapi.cpp:5019 19 xul.dll nsXPCWrappedJSClass::CallMethod js/src/xpconnect/src/xpcwrappedjsclass.cpp:1700 20 xul.dll nsXPCWrappedJS::CallMethod js/src/xpconnect/src/xpcwrappedjs.cpp:588 21 xul.dll PrepareAndDispatch xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:114 22 xul.dll SharedStub xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:141 23 xul.dll nsEventListenerManager::HandleEventSubType content/events/src/nsEventListenerManager.cpp:1114 More reports at: http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=FFPlugin.dll%400x19d0c4 http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=_purecall%20|%20FFPlugin.dll%400x19d0c8 http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=FFPlugin.dll%400x19caa4
blocking2.0: --- → ?
Assignee: nobody → kev
blocking2.0: ? → final+
Whiteboard: [softblocker]
With combined signatures, it is now a virtual #5 top crasher in 4.0b10 over the last week.
Can someone provide the block ranges and GUID that we need to block for this?
Whiteboard: [softblocker] → [softblocker][Needs block ranges]
> Can someone provide the block ranges and GUID that we need to block for this? extension id: firefox@bandoo.com version: 5.0 Firefox versions: 3.7a1pre and higher
Kev, can you reach out to them? Softblocked on staging: <emItem id="firefox@bandoo.com"> <versionRange minVersion="5.0" maxVersion="5.0" severity="1"> <targetApplication id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"> <versionRange minVersion="3.7a1pre" maxVersion="*"/> </targetApplication> </versionRange> </emItem>
Whiteboard: [softblocker][Needs block ranges] → [softblocker][Needs outreach][Needs testing][Block planned for 2/11]
Not many avenues available. Their "terms@bandoo.com" email bounces, so I have filed a notice about the crashers and this bug through their "Contact Us" link on the website and to support@bandoo.com. I'll update if I hear anything back.
Depends on: 633609
Once bug 633609 is fixed to update the website, I'll push this live.
Assignee: kev → fligtar
OS: Windows XP → All
Hardware: x86 → All
Whiteboard: [softblocker][Needs outreach][Needs testing][Block planned for 2/11] → [softblocker][Block planned for 2/11]
Blocks: 608378
According to bug 608378, it would be good to also block-list it in 3.6.
Depends on: 523784
Now it is #6 top crasher in 4.0b11 and #15 top crasher in 3.6.13. If you add bug 608378 signature, it is #3 top crasher in 4.0b11 and #4 top crasher in 3.6.13.
blocking1.9.2: --- → ?
Summary: Crash [@ FFPlugin.dll@0x19d0c4 ][@ _purecall | FFPlugin.dll@0x19d0c8 ][@ FFPlugin.dll@0x19caa4 ] with Bandoo 5.0 → Crash [@ FFPlugin.dll@0x19d0c4 ][@ _purecall | FFPlugin.dll@0x19d0c8 ][@ FFPlugin.dll@0x19caa4 ][@ FFPlugin.dll@0x19cf04 ][@ FFPlugin.dll@0x173ee4 ][@ FFPlugin.dll@0x174524 ][@ FFPlugin.dll@0x175244 ][@ FFPlugin.dll@0x173ed4 ] with Bandoo 5.0
Sure, please blocklist for FF3.6, but it doesn't need to block the release.
blocking1.9.2: ? → ---
status1.9.2: --- → wanted
What's the status here? Bug 633609 is fixed, and this whiteboard says the block is planned for 2 weeks ago.
Depends on: 637448
Whiteboard: [softblocker][Block planned for 2/11] → [softblocker]
Blocked in production. Since it's a bit late at night, my number is in the Mozilla phonebook if there are any issues.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
No longer blocks: 608378
It is supposed to have been fixed since March 1st, but it is not. Some people still crashes on March 5th: Signature FFPlugin.dll@0x19d0c4 UUID 8a2539b7-5345-43d7-8370-621d32110305 Time 2011-03-05 06:53:15.423691 Uptime 256 firefox@bandoo.com 5.0 The crash number for FFPlugin.dll@0x19d0c4 signature does not decrease significantly (some crashes are due to long sessions started before the blocklisting): 20110305: 256 20110304: 265 20110303: 397 20110302: 665 20110301: 595 20110228: 544 20110227: 345 20110226: 60
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This is trending down; it's probably just taking a while for the blocklist entries to make their way out to users.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
If this doesn't continue to trend down, please reopen.
hard to say if this is having a significant overall impact on FFPlugin.dll crashes. they are down from the first of the month, but still at about the same level as early feb. date crashes at FFPlugin.dll 20110201 2170 20110202 2071 20110203 2555 20110204 2489 20110205 2281 20110206 2223 20110207 2591 20110208 2592 20110209 2514 20110210 2443 20110211 2228 20110212 2144 20110213 2658 20110214 2408 20110215 2289 20110216 2808 20110217 2714 20110218 2804 20110219 2570 20110220 2780 20110221 2808 20110222 2695 20110223 2921 20110224 2945 20110225 2822 20110226 2824 20110227 2984 20110228 2956 20110301 2912 20110302 2700 20110303 2298 20110304 2051 20110305 2081 20110306 2144 20110307 2104 I think we need to look for more posible things to block. seeing if I can get some data...
it looks like in Bug 633609 we only blocked Bandoo to version 5.0 or at least thats what http://www.mozilla.com/en-US/blocklist/ shows Bandoo, version 5.0 for Firefox 3.6a1pre and higher. Reason: high crash volume (see bug 629634) I'm seeing a 95%+ hit rate on FFPluing.dll crashes where Bandoo 6.0 is around. Was there a reason we decided not to block 6.0? ./get-module-info.sh FFPlugin.dll BandooRes.dll 20110307* http://crash-stats.mozilla.com/report/index/0c2de74f-a2c7-4fc0-96d2-193002110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0bfa4ae6-b512-4e2d-8231-aa4222110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0bd50471-bff2-4544-bc4e-21ed62110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0bced268-bc18-4818-aaaf-6e80e2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0bc70417-307c-43ed-8043-98ce42110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0bc55ae8-6c65-464f-8dde-be0e32110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b9a6cd9-811c-4390-a181-f5ab82110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b8b9314-a20b-4b2c-8ebc-88e802110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b6561f6-4b83-4c8b-9b98-39f8c2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b5e6cda-7e3d-41b7-85d5-420cf2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b5c7381-693e-495e-b4d9-aa5952110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b59d12d-0f7a-41a0-8606-be5582110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0b2a9e03-7833-4e00-b948-f331c2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0ae9f2c5-eb74-422c-b160-f2dd22110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0ab0e86a-51c8-4c28-a83e-e23432110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a769a72-6a8b-47f2-b3bd-46a392110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a5f725c-e86b-4e6b-8a2f-ec2fc2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a3aa6ac-0cef-4208-8e6e-7f21a2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a2086a9-415f-4a08-b4e5-e6e7e2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a1e8f9b-cf4e-4f28-b5f1-d22612110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a128857-6b5d-4f6b-88db-a54bb2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0a0e5af2-915b-4542-bb09-660672110307 http://crash-stats.mozilla.com/report/index/09f63fad-9dd3-4f24-9c3c-644c42110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/09f217be-dfcd-45c4-9310-3a8642110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/09b11b42-72a7-4f40-a6cd-509482110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/09af94e2-8beb-4a80-82cf-8c0d62110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/09ac90e3-8f45-40d7-9639-565922110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/097ce5c2-525b-4ae4-b239-813972110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0968781e-e23c-4778-9dc7-9407c2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/094f66e4-7276-4174-be0f-643c92110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/09484661-f4c4-4925-b199-e96a92110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/092dc2a1-3244-4bc5-a514-92c2e2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/090f691b-493e-47c4-9fdc-1a16a2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/090abd7b-b13e-47bf-9492-755d12110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/08e70583-24a6-44e1-a1f7-e37092110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/08d7c348-12c5-4ac3-8f40-8e5012110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/08c23ffa-af07-4706-8422-ee9a82110307 http://crash-stats.mozilla.com/report/index/08948d98-51ec-476f-b740-8451e2110307 BandooRes.dll 6.0.0.0 http://crash-stats.mozilla.com/report/index/0870aac2-19fd-47a6-ba45-ecaa22110307 BandooRes.dll 6.0.0.0
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
out of 1000 FFPlugin reports we also have some addons that might be named only by uuid that are installing the bandoores.dll that show up in high volume. 255 {7FF99715-3016-4381-84CE-E4E4C9673020}</td 1.0 CLSID: {7FF99715-3016-4381-84CE-E4E4C9673020} Name: Searchqu Toolbar Filename: SearchquDx.dll Location: %ProgramFiles%\Windows Searchqu Toolbar\ToolBar Description: Searchqu Toolbar, stealth installed, bundled with software from bandoo.com 170 {972ce4c6-7e08-4474-a285-3208198ce6fd}</td 3.6.15 137 {1FD91A9C-410C-4090-BBCC-55D3450EF433}</td 2.0 shareazaweb search plugin? FF - prefs.js..browser.search.selectedEngine: "Shareaza Web Search" FF - prefs.js..browser.search.useDBForOrder: true FF - prefs.js..browser.startup.homepage: "http://search.shareazaweb.com/" FF - prefs.js..extensions.enabledItems: {1FD91A9C-410C-4090-BBCC-55D3450EF433}:2.0 76 {972ce4c6-7e08-4474-a285-3208198ce6fd}</td 3.6.13 55 m3ffxtbr@mywebsearch.com</td 1.1 32 {ABDE892B-13A8-4d1b-88E6-365A6E755758}</td 14.0.1 31 {1FD91A9C-410C-4090-BBCC-55D3450EF433}</td 1.0 30 {99079a25-328f-4bd4-be04-00955acaa0a7}</td 4.1.0.01 28 {972ce4c6-7e08-4474-a285-3208198ce6fd}</td 3.6.14 26 {7b13ec3e-999a-4b70-b9cb-2617b8323822}</td 2.7.1.3
In reply to comment 17 > Was there a reason we decided not to block 6.0? The extension version of Bandoo 5.0 & 6.0 (dlls versions have not been analyzed) is 5.0 and the extension blocklisting has been preferred. The related dlls (FFPlugin.dll, BandooRes.dll) seems to load with or without the extension.
Over to me to give blocklist specifics.
Assignee: fligtar → clegnitto
Summary: Crash [@ FFPlugin.dll@0x19d0c4 ][@ _purecall | FFPlugin.dll@0x19d0c8 ][@ FFPlugin.dll@0x19caa4 ][@ FFPlugin.dll@0x19cf04 ][@ FFPlugin.dll@0x173ee4 ][@ FFPlugin.dll@0x174524 ][@ FFPlugin.dll@0x175244 ][@ FFPlugin.dll@0x173ed4 ] with Bandoo 5.0 → Crash [@ FFPlugin.dll@0x19d0c4 ][@ _purecall | FFPlugin.dll@0x19d0c8 ][@ FFPlugin.dll@0x19caa4 ][@ FFPlugin.dll@0x19cf04 ][@ FFPlugin.dll@0x173ee4 ][@ FFPlugin.dll@0x174524 ][@ FFPlugin.dll@0x175244 ][@ FFPlugin.dll@0x173ed4 ] with Bandoo 5.0 or 6.0
(In reply to comment #19) > In reply to comment 17 > > Was there a reason we decided not to block 6.0? > The extension version of Bandoo 5.0 & 6.0 (dlls versions have not been > analyzed) is 5.0 and the extension blocklisting has been preferred. > The related dlls (FFPlugin.dll, BandooRes.dll) seems to load with or without > the extension. So if we blocked 5.0 and 6.0 using just the 5.0 block (as they both do seem to identify as 5.0 in the extension, even though the dll identifies as 6.0.0.0), what is there left to do here? Block the dll? If so that's in product and can't be done with the web blocklist and this should be a ride-along at most if we do a RC2 and a .x at least. I also see crashes in 3.6.15 in comment 17, so perhaps the previous block should have included 3.6.
In reply to comment 21 > I also see crashes in 3.6.15 in comment 17, so perhaps the previous block > should have included 3.6. It has included 3.6: Bandoo, version 5.0 for Firefox 3.6a1pre and higher. Reason: high crash volume https://www.mozilla.com/en-US/blocklist/ > what is there left to do here? Block the dll? Yes, but even with it, it can not necessarily work if the DLL loads through AppInit_DLLs: see bug 614966. > If so that's in product and can't be done with the web blocklist and this > should be a ride-along at most if we do a RC2 and a .x at least. I nominate it.
blocking2.0: final+ → ?
It's only blocked in 4.0 until the softblock backport is shipped in a 3.6 update. We're still not softblocking anything in 3.6.
blocking2.0: ? → .x+
Hello, My name is Michael, I'm running the Bandoo project and trying to resolve this issue which is currently a highest priority for our development team. Sorry for the delay, we had some issues getting your mail. We couldn't reproduce this crash on our side and need a some additional information. Do you have information about: 1. Full versions of Bandoo that crashed (including build number) or date when the crash reports started to arrive 2. Is this crash relevant for all FF versions or just started from some specific version? 3. Is it crashes when user is in some specific website? Maybe it crashes more in some sort of websites? I'm available to answers any of your questions if you need. Thanks a lot, we appreciate your help. Michael.
In reply to comment 24 > 1. Full versions of Bandoo that crashed (including build number) or date when > the crash reports started to arrive Here is the FFPlugin.dll debug identifier by crash signature: FFPlugin.dll@0x19d0c4: BDA660F88D064455BA194E51501A3ACF1 FFPlugin.dll@0x152bd4: BDA660F88D064455BA194E51501A3ACF1 FFPlugin.dll@0x19caa4: BDA660F88D064455BA194E51501A3ACF1 _purecall | FFPlugin.dll@0x152bd8: C8B07E8F86AC46A687DA92C9178E25341 _purecall | FFPlugin.dll@0x19d0c8: BDA660F88D064455BA194E51501A3ACF1 @0x0 | NS_InvokeByIndex_P: BDA660F88D064455BA194E51501A3ACF1 NS_InvokeByIndex_P: BDA660F88D064455BA194E51501A3ACF1 > 2. Is this crash relevant for all FF versions or just started from some > specific version? It happens in Firefox 3.0, 3.5, 3.6, 4.0RC1.
Chris, can you answer to question 3 in comment 24?
I think we found the problem and gonna release the a fixed version later today. I'll keep you updated.
Thanks all. We released the fix a couple of hours ago. I beleive the number of crashes will reduce significantly in a couple of weeks. I'll also check an option of upgrade to accelerate this process.
With combined signatures, it is #16 top crasher in 4.0.1. Here is the correlations by extension version for each top crash signature: * ffplugin.dll@0x19d0c4: 94% (166/176) vs. 1% (854/74907) firefox@bandoo.com 94% (166/176) vs. 1% (735/74907) 5.0 0% (0/176) vs. 0% (119/74907) 5.1 * NS_InvokeByIndex_P: 81% (50/62) vs. 1% (854/74907) firefox@bandoo.com 81% (50/62) vs. 1% (735/74907) 5.0 0% (0/62) vs. 0% (119/74907) 5.1 * ffplugin.dll@0x152bd4: 94% (60/64) vs. 1% (854/74907) firefox@bandoo.com 92% (59/64) vs. 1% (735/74907) 5.0 2% (1/64) vs. 0% (119/74907) 5.1 * _purecall | ffplugin.dll@0x19d0c8: 94% (46/49) vs. 1% (854/74907) firefox@bandoo.com 94% (46/49) vs. 1% (735/74907) 5.0 0% (0/49) vs. 0% (119/74907) 5.1 * ffplugin.dll@0x19caa4: 92% (22/24) vs. 1% (854/74907) firefox@bandoo.com 92% (22/24) vs. 1% (735/74907) 5.0 0% (0/24) vs. 0% (119/74907) 5.1 The ffplugin.dll@0x152bd4 crash signature is not fixed in the Bandoo extension version 5.1.
Summary: Crash [@ FFPlugin.dll@0x19d0c4 ][@ _purecall | FFPlugin.dll@0x19d0c8 ][@ FFPlugin.dll@0x19caa4 ][@ FFPlugin.dll@0x19cf04 ][@ FFPlugin.dll@0x173ee4 ][@ FFPlugin.dll@0x174524 ][@ FFPlugin.dll@0x175244 ][@ FFPlugin.dll@0x173ed4 ] with Bandoo 5.0 or 6.0 → Crash [@ ffplugin.dll@0x19d0c4 ][@ _purecall | ffplugin.dll@0x19d0c8 ][@ ffplugin.dll@0x19caa4 ][@ ffplugin.dll@0x19cf04 ][@ ffplugin.dll@0x173ee4 ][@ ffplugin.dll@0x174524 ][@ ffplugin.dll@0x175244 ][@ ffplugin.dll@0x173ed4 ] with Bandoo 5.0 or 6.0
We are investigating this. For now it looks like this happens on our older versions and not on the fixed one. We are updating this version. Do you see number of reports goes down?
(In reply to comment #31) > Do you see number of reports goes down? For the last 4 days, I haven't seen any correlations with Bandoo 5.1 for the ffplugin.dll@0x152bd4 crash signature. So it seems to be fixed.
So the problem is gone now?
(In reply to comment #33) > So the problem is gone now? After checking today's correlation file, I see it for another crash signature (but not in the yesterday one): ffplugin.dll@0x19cf04|EXCEPTION_ACCESS_VIOLATION_READ (26 crashes) 88% (23/26) vs. 1% (1926/139909) firefox@bandoo.com 85% (22/26) vs. 1% (1665/139909) 5.0 4% (1/26) vs. 0% (261/139909) 5.1
Whiteboard: [softblocker] → [softblocker][fixed by Bandoo extension 5.1]
We'll check this.
From what we see all relevnt signatures are from very old Bandoo versions that are not distributed anymore.
Per comment 36, I close it as fixed.
Assignee: clegnitto → nobody
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Component: Blocklisting → Extension Compatibility
Product: addons.mozilla.org → Firefox
QA Contact: blocklisting → extension.compatibility
Resolution: --- → FIXED
Crash Signature: [@ ffplugin.dll@0x19d0c4 ] [@ _purecall | ffplugin.dll@0x19d0c8 ] [@ ffplugin.dll@0x19caa4 ] [@ ffplugin.dll@0x19cf04 ] [@ ffplugin.dll@0x173ee4 ] [@ ffplugin.dll@0x174524 ] [@ ffplugin.dll@0x175244 ] [@ ffplugin.dll@0x173ed4 ]
You need to log in before you can comment on or make changes to this bug.