Firefox 33 crashes after exiting since update to Avast 2015

[Gopher John]

https://bugzilla.mozilla.org/show_bug.cgi?id=1087674

Yaron 10,
Thanks for filing the bugzilla report.

I have a thread on Mozillazine Forum concerning this.  http://forums.mozillazine.org/viewtopic.php?f=38&t=2882327

[REDACTED]

My pleasure.
And thanks for the link to the post on Mozillazine Forum.

You can register to Bugzilla, and CC yourself to that bug.

[miguelgrado]

Yesterday, I updated Avast Internet Security via AvastUI from Avast 9.0.2021 to Avast 2015 10.0.2206 on both my machines.  I had Avast Online Security installed but disabled in all profiles.  The crashing is consistent; close Firefox clicking the x at the top right of the program window, and a minute or so later Firefox crash reporter will come up.

I have uninstalled AOS on this Toshiba via the Uninstall procedure, waited a short while and then restarted the machine in the hope that this would fix the problem.  No such luck.  I haven't yet done a clean uninstall and then reinstalling, in case Avast Team might want any information from my installs.

Idem +1 

[mchain]

https://bugzilla.mozilla.org/show_bug.cgi?id=1087674

Confirmed.  Seems to crash only when command to close browser is used (mouse click red X), as bug report indicates.

See attached below:

Thanks for the link.

[REDACTED]

I'm also experiencing FF 33 crash problem. FF 33 freezes and I need to press the restart button to get my pc working..

[RejZoR]

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...

[Gopher John]

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.

[RejZoR]

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).

[REDACTED]

Version 2015  sometimes freezes Opera...........!!!!!!!!!!!!!

[REDACTED]

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.

[REDACTED]

@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.

[Gopher John]

[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.

[REDACTED]

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.

[REDACTED]

"Add-on manager -> Check for (installed) updates" consistently crashes FF.
I does not happen with "https scanning" disabled in Avast.

[RejZoR]

Seems like turning off HTTPS Scanning indeed solves the issue. Haven't had a crash since...