Looking at
http://crash-stats.mozilla.com/report/index/4f9f634d-19a8-4437-8859-8d3e12100619The crash occurred in TFWAH.dll, a ThreatFire module that is part of ThreatFire's "Active Defense Technology". From the WinPatrol Plus database:
ThreatFire Service – TFWAH.EXE
Tfwah.dll, tfgui.dll, and tfservice.exe install with ThreatFire from PC Tools. ThreatFire (formerly CyberHawk) and ThreatFire Pro promise to use "Active Defense Technology" to protect you from viruses, Trojans, and other types of malware including those that are not yet known to regular antivirus programs. This is intended as real-time protection so you'll need to leave this tfservice.exe running if you want the protection this program promises. You'll find more information at http://www.threatfire.com/.
# Safe
There may be a bug in the ThreatFire module. See if there's a more recent version of ThreatFire available. It may not have that problem. If you get any more Firefox crashes which occur in that module, then I suggest turning off that ThreatFire service.
1. Why would FlashPlayer introduce an update that had this effect?
- Coincidence?
- Problematic interaction between Flash and ThreatFire?
- Bug in new Flash version?
- Something unique to the problematic
BUSINESS BULLET's Flash player or content? (This would be my first guess, especially if the problem stays fixed with that custom Adblock Plus filter. The previous scenarios are possible too but harder to confirm.)
2. I am curious to learn how you pinpointed the problem so quickly?
- In my experience, CPU problems caused by visiting a web page are usually caused by Flash content.
- I typically use NoScript with
NoScript Options > Embeddings > Apply these restrictions to whitelisted sites too checked.
- According to NoScript, BUSINESS BULLET is the only Flash object on the web page.
- Allowing the Flash object to run by clicking on its NoScript placeholder caused my CPU to jump to 100% and stay there. (I have a slow computer, so it may not jump that high for other people.)
- The Adblock Plus blockable items pane shows that
http://www.telegraph.co.uk/telegraph/template/utils/ooyala/telegraph_player.swf is the only url with type
object on that page. It's the same url that NoScript displayed in the placeholder tooltip before I clicked it.
I ask, because it is frustrateinf incidents like these that have caused me (and probably many other born button-pushers!!) to take drastic measures like messing with the Registry (I think I wrecked my old laptop "doctoring" around with it - trying dodgy anti-spyware and registry fixes.)
I agree. Nothing like buying software which promises to "boost your speed" by cleaning the registry! Aack!
However here is that crash report ID - it may tell you more:
bp-4f9f634d-19a8-4437-8859-8d3e12100619 19.06.2010 14:37 - on the report itself it reads as:
ID: 3ea0cc6b-fbf9-4632-8026-b6d932100615
It tells me nothing of course, but it may tell you something useful. It mentioned "ns" a few times and "Plug-ins" - which ? FP?
Hard to tell. I think "ns" stands for Netscape, an ancestor of Firefox. By the way, since it doesn't matter, the second id is for a crash which occurred four days earlier on 2010-06-15. It crashed in the ThreatFire module too.
Anyway Firefox started to work normaly immediately after it restarted and before I took your ABP filter advice. So possibly Firefox kicked out whatever was jamming it anyway?
I hope so. I wouldn't be concerned about that issue anymore unless it recurs. (But keep that BUSINESS BULLET blocked with Adblock Plus.)