The anti-virus/anti-malware stuff might do something if it's a well known attack signature, but the well-funded players can generate hundreds of new mutations daily that are specifically designed to avoid triggering these software packages. More importantly, it's trivial to compromise a machine running Windows XP through numerous attack vectors. If it continues to work, great - but if and when it breaks, it's extremely unlikely that we're going to do work to fix those bugs. The reality is simply that we're not working on XP anymore. If you haven't already, you could reboot and see if the browser starts working more normally again, but you're really a sitting duck on this configuration. We're really not testing it, and are only going to fix critical security issues at this point. WinXP is very, very broken from a security perspective and has reached it's end of life. Windows 8 and higher provide more modern defenses, but I understand that moving to the newest thing isn't always attractive. Windows 7 provides a set of reasonable memory protections, and is really the minimum Windows version you should be on given the threat landscape in 2014. This probably isn't going to be the answer you're looking for, but I'd highly recommend taking this opportunity to move away from WinXP. As we're not seeing a flood of similar reports (we're on 98% of computers browsing the web), there's definitely something pretty unique about your system that leads to this issue. Given the degree to which you're currently exposed to malware infections by virtue of being on WinXP SP2 (which pre-dates all modern memory-based malware defenses), I wouldn't be surprised if you were seeing side effects from an infection however, it's hard to make that kind of diagnosis from where I'm sitting. What I can tell, is that things aren't working like they should. The libraries are super simple, standard libraries that would not be slow under normal circumstances. It doesn't really do much but relay messages, so it should just work. The crash you're seeing is in the Firefox process that's hosting the Flash Player plug-in. Unfortunately, the information above isn't really helpful in performing a diagnosis. Hopefully I've provided enough information for some assistance. Here are a couple of the script error messages as well. You can stop the plugin now or you can continue to see if the plug in will complete Shockwave flash may be busy or may have stopped responding (ox80000003) occurred in the application at location ox002b141b Hopefully I'm overlooking something or someone knows what I need to do. I have already did trouble shooting with Adobe's suggestions, Mozilla's suggestions, and Zygna's suggestions to no avail. I am using Mozilla Firefox 31 and Shockwave Flash 14.0.0.145 I frequently have crashes and am receiving the following error messages. I've experienced a number of problems since the download. Zygna Games required the download of Flash 14 to continue playing their online games via Face Book or their own website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |