Firefox crashes when trying to load a site, loads others just fine
Been having issues with Firefox crashing upon attempting to load this site: https://www.shrinemaiden.org/forum/
Crash Report IDs: bp-3046b686-f27e-4f75-b0a3-a31610191109 bp-ebd93e16-1405-4d5d-a0fa-7fae50191109 bp-90748c90-367c-4386-95b8-eb8210191109 bp-44a440c7-e3fc-497b-9641-0c44f0191109 bp-709d1e2b-576f-4289-ad35-9077d0191109 bp-62344577-627e-4541-93e9-ff3500191109 bp-689a7385-685d-4090-9613-841320191109
What happens is that it tries to load, comes up with message saying it has trouble trying to find the address before the browser stops and crashes after a few seconds. I've tried clearing cookies, disabled add-ons, turning on/off hardware acceleration and updating Firefox but nothing worked. Every other site loads fine but this one doesn't.
Todas as respostas (14)
Hi Felis-Licht, The certificate for shrinemaiden.org expired yesterday and is being blocked by Firefox. Also, the Crash Reports indicate an engine for Norton Security caused the crash.
My_Cheese_Is_Slippin' said
Hi Felis-Licht, The certificate for shrinemaiden.org expired yesterday and is being blocked by Firefox. Also, the Crash Reports indicate an engine for Norton Security caused the crash.
I was aware that the certificate expired as I had stored an exception for it before (even cleared it to see if that was causing the crashing), but now Firefox is blocking it altogether? Why is that?
I also don't understand how Norton could be causing the crash, could you elaborate more on that please?
The crash report indicated that Norton Intrusion Prevention engine was the cause of the crash. You can check Norton's installation by selecting Help and then Get Support. It will scan it's installation, check for updates, check for definitions and repair itself, if necessary. Some Registry cleaners can cause corruption of Norton's installation files, so, if you use one of those check things out thoroughly and set exceptions if you need to.
I can't explain the issue with the certificate. Maybe, if you check that Norton is OK and try the certificate again it will work.
My_Cheese_Is_Slippin' said
The crash report indicated that Norton Intrusion Prevention engine was the cause of the crash.
That DLL is flagged, but it might not be the only factor. Some other users have reported crashes with the same signature that do not list a Norton DLL. There's no way for the public (non-privileged users of the crash stats site) to see whether the issue was on the same site.
My_Cheese_Is_Slippin' said
The crash report indicated that Norton Intrusion Prevention engine was the cause of the crash. You can check Norton's installation by selecting Help and then Get Support. It will scan it's installation, check for updates, check for definitions and repair itself, if necessary. Some Registry cleaners can cause corruption of Norton's installation files, so, if you use one of those check things out thoroughly and set exceptions if you need to. I can't explain the issue with the certificate. Maybe, if you check that Norton is OK and try the certificate again it will work.
I checked out Norton and it says it fixed the installation (that was the only thing that came up), and I ran it again just to be sure everything was fixed. Tried loading the site again and it still crashed. Latest crash log: bp-18ed5a56-063e-4fca-8f6a-62fa50191111 I don't recall cleaning the Registry or anything though that would cause corruptions.
Also checked the Registry today, came up with the message, "windows resource protection did not find any integrity violations". So it can't be the Registry then
It's still crashing btw, nothing I've done has fixed it: bp-7aab1819-818c-455e-8721-911060191112
The crash reports aren't related to Symantec (Norton) software as far as I can tell, but are about IPC (Inter-Process Communication). Only the last report you posted is recent (Nov 12), all other reports are from the beginning of October with Firefox 69.0.1.
- Firefox 70.0.1 Crash Report [@ mozilla::ipc::IProtocol::ChannelSend ]
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Safe Mode start window
cor-el said
The crash reports aren't related to Symantec (Norton) software as far as I can tell, but are about IPC (Inter-Process Communication). Only the last report you posted is recent (Nov 12), all other reports are from the beginning of October with Firefox 69.0.1.Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- Firefox 70.0.1 Crash Report [@ mozilla::ipc::IProtocol::ChannelSend ]
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Safe Mode start window
I tried Safe Mode, it still crashes when trying to access the site.
Note that a modules being flagged with a red background merely means that the Socorro server doesn't have symbols for this file and isn't able to cross reference to a function in the source code. Security software hardly (or never) makes symbols available as this would make it easy to understand its code.
You can create a new profile to test if your current profile is causing the problem. You can easily revert via the Profile Manager to your current profile, so this is just for testing whether this is caused by your current profile.
See "Creating a profile":
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
cor-el said
Note that a modules being flagged with a red background merely means that the Socorro server doesn't have symbols for this file and isn't able to cross reference to a function in the source code. Security software hardly (or never) makes symbols available as this would make it easy to understand its code.
You can create a new profile to test if your current profile is causing the problem. You can easily revert via the Profile Manager to your current profile, so this is just for testing whether this is caused by your current profile.
See "Creating a profile":
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
I created a new profile without transferring any of old files over and it still crashes trying to load the site.
This issue is still present, it still crashed on a new profile. Recent crash log: bp-660f17e2-a868-46d0-a000-96b180191121
The site still doesn't have a valid certificate. I wonder whether there is a reliable source for what is happening with that site, whether it is working for others or has been hacked.
jscher2000 said
The site still doesn't have a valid certificate. I wonder whether there is a reliable source for what is happening with that site, whether it is working for others or has been hacked.
They've had issues with the certificate expiring before, and more recently it's kinda been happening more than once when it was only once every other year or so. I've already alerted them about it, but what doesn't make sense to me is why I can store an exception and access the site just fine on mobile but desktop crashes regardless of there being an exception or not (doesn't help that other users there have no issues and can still access the site.)