Though i’m not sure reporting it to Mozilla is the way to go. After all, Firefox 33 wasn’t crashing with older avast! 2014, which means it’s not really Mozilla’s fault for the crashing.
I think it has something to do with either HTTPS scanning part or the Script Scanning. I’ve disabled them both now and i’ll be observing. If FF doesn’ crash anymore, it’s this. Then it’s up to avast! to fix it… because FF 33 alone worked without a single crash for me before avast! 2015. I’ve even posted that during beta but they apparently missed my report…
I’ve disabled https scanning in WebShield, and Firefox is no longer hanging and crashing on close. It now closes promptly. Apparently, Avast has work to do on HTTPS scanning.
Seems like the certificate or something else hangs FF 33 and causes it to crash afterwards. Can’t really get anything useful from Event Viewer since nothing from Firefox crashes is logged there (which is really weird).
Just wanted to add that I’m seeing the exact same issues with the latest Avast! and FireFox 33.
Not sure if this is useful to help troubleshoot, but after updating Avast yesterday every HTTPS url I visited in FireFox complained about the SSL cert. Even sites like Google. I restarted my machine again and FireFox stopped complaining about the certificates (although it keeps crashing or refuses to shut down as reported in this thread).
EDIT: Should also add that disabling HTTPS scanning in Avast made the problem go away.
@mchain,
You’re welcome.
Could you please register to Bugzilla and send your Crash Reports (in the aforementioned bug)?
@RejZoR,
Thanks for the information.
Your argument makes sense. Still, I think it’s important to keep reporting to Mozilla. They have already found a possible cause in their code.
@Gopher John
Could you please post some links to https sites which trigger the crash?
Also, could you re-enable “https scanning” and recheck the issue?
It’s weird, but in the last hour I haven’t been able to trigger a crash.
I used to terminate FF before the Crash Manager came up, and I don’t have any crash reports.
@All,
Two lightweight applications for easily detecting if a program has not properly closed. SysTrayMeter ProcessCounter. If you like it, please thank the dev.
[quote author=Yaron10 link=topic=157675.msg1139594#msg1139594 date=1414087194 @Gopher John
Could you please post some links to https sites which trigger the crash?
Also, could you re-enable “https scanning” and recheck the issue?
It’s weird, but in the last hour I haven’t been able to trigger a crash.
I used to terminate FF before the Crash Manager came up, and I don’t have any crash reports.
[/quote]
I’ve already posted several crash links this morning. The bugzilla report has no indication that they have a possible cause for the crash, other that that I was asked to disable WebShield. Instead, I opted to only disable https scanning in the WebShield which stopped the crashing.
If you closed Firefox in Task Manager or exited the Windows user account or shut down Windows before the crash reporter came up, there would be no report nor would one even know if there was a problem. My first indication was when I closed Firefox and then noticed that I’d received an email message with Pegasus Mail. I clicked on the link in the email and that’s when I found out Firefox was hanging in the background.
I’ve asked for links to sites that cause a crash. I’ve visited several https sites and FF didn’t crash.
If we want to pinpoint the problem, it would be a good idea to re-enable “https scanning” and recheck the issue.
I know that if I terminate FF before the Crash Reporter comes up there would be no crash reports.
I just explained why I didn’t post any in Bugzilla.
I don’t know if they have found a possible cause to the crash, but it led to an issue which should be fixed.
I can’t pin the problem to any particular web sites. With https scanning activated, Firefox routinely crashes on closing regardless of sites visited, length of browsing session, or Firefox profile used. I don’t think that it is Mozilla’s problem at all. Avast’s https scan holds on to the Firefox process while it is trying to close, resulting in the crash. Firefox does some housekeeping on close, and probably isn’t allowed to complete the process.
Getting this also. I am sure it has to do something with the new Avast update. Firefox 33 was released last week, I had only 3 crashes all of 2014 doug did. Since updating Avast, I get it multiple times a day b/c I close and reopen Firefox pretty often.
Thanks.
On my system many HTTPS sites don’t cause a crash.
As I’ve mentioned - “Add-on manager → Check for (installed) updates” consistently crashes FF with “https scanning” enabled.
Open the Avast interface. Go to Settings → Active Protection (I use a localized Avast. The original English might be different.) → Web Shield → Customize.
Disable “https scanning”.
Thx for the tip, this will work for now, but just stating the obvious that this needs to be fixed. It doesn’t look like it is exclusively Firefox 33, Firefox 31 esr also crashes. I think it might have to do with something about how Avast is hooking into Firefox to scan for https, not letting it go fast enough.
Is Firefox crashing when visiting a specific https site or checking for updates immediately or shortly thereafter? I’m not having any crashes while Firefox is running at all, only on closing.
By the number of your posts here you must be more familiar with Avast and its developers than I am.
Isn’t it somewhat strange we haven’t received any response from Avast team? - This is a major issue.
BTW, About 5 minutes ago Adobe Flash Player crashed. This didn’t happen to me for a very long time.
