Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Gopher John on October 22, 2014, 09:32:41 PM
-
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.
-
It's often happening with or without AOS. And the main thing i hate about it, ZERO entries in Event Viewer. Which sucks balls to debug. I usually find out instantly what was going on through Event Viewer, but not here. But since i was using FF 33 before and all was fine, after updating to Beta and RC builds, it was crashing.
-
Something is wrong with Firefox 33.I had that problem before I updated Avast to
the latest version.Also some bugs in Firefox are present in Windows XP, but not in Windows 7.
Soon there will be version 33.0.1 so I guess we will see if the culprit was Firefox.
-
abruptum,
Where did you get the information that Firefox 33.0.1 forthcoming and will be released soon? I don't see any mention on Firefox forums.
Before yesterday's Avast 2015 update, the last Firefox crash I had was in March 2014.
-
I have Firefox 33 and have no crashes.
Try typing about:crashes into the address bar.
-
Firefox 33.0.1 RC1
http://www.softpedia.com/get/Internet/Browsers/Mozilla-Firefox-Final.shtml
-
I have Firefox 33 and have no crashes.
Try typing about:crashes into the address bar.
I have several listed there, most of them yesterday and today. No extensions have updated during that time. However, I started Firefox in Firefox Safe Mode and it did not crash on exit.
-
Firefox 33.0.1 RC1
http://www.softpedia.com/get/Internet/Browsers/Mozilla-Firefox-Final.shtml
I wonder where that file originated. It is not listed on any of the Mozilla ftp sites, nor any other official Mozilla sites. I wouldn't trust it.
-
I'm averaging one submitted crash report per day since October 17. Before that I had 4 crashes in all of 2014.
-
I'm averaging one submitted crash report per day since October 17. Before that I had 4 crashes in all of 2014.
So this has been happening with you even before the release of avast 2015?
-
Had the same problem after updating a windows 8.1 and 8 system. Solved by unchecking enable https setting under web shield setting.
-
Firefox 33.0.1 RC1
http://www.softpedia.com/get/Internet/Browsers/Mozilla-Firefox-Final.shtml
I wonder where that file originated. It is not listed on any of the Mozilla ftp sites, nor any other official Mozilla sites. I wouldn't trust it.
http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/33.0.1-candidates/build1/win32/en-US/
-
I've also experienced some crashes after updating to 2015 10.0.2206 and closing FF 33.
Win 7 32-bit.
-
http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/33.0.1-candidates/build1/win32/en-US/
Thanks. Perhaps a few days for official release. :) I hope this update fixes the problem.
-
https://bugzilla.mozilla.org/show_bug.cgi?id=1087674
-
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 (http://forums.mozillazine.org/viewtopic.php?f=38&t=2882327)
-
My pleasure. :)
And thanks for the link to the post on Mozillazine Forum.
You can register to Bugzilla, and CC yourself to that bug.
-
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 :(
-
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.
-
I'm also experiencing FF 33 crash problem. FF 33 freezes and I need to press the restart button to get my pc working..
-
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).
-
Version 2015 sometimes freezes Opera...........!!!!!!!!!!!!!
-
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 (http://freewaregenius.com/wp-content/downloads/SysTrayMeter.zip)
ProcessCounter (http://www.sevenforums.com/software/317043-number-processes-system-tray-3.html). 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.
-
"Add-on manager -> Check for (installed) updates" consistently crashes FF.
I does not happen with "https scanning" disabled in Avast.
-
Seems like turning off HTTPS Scanning indeed solves the issue. Haven't had a crash since...
-
Thanks again. :)
-
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.
-
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.
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.
-
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.
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".
-
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.
-
You're welcome.
I do hope the developers are aware of the issue.
-
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.
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.
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.
-
Only on closing. I wasn't clear enough.
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.
-
I too am having firefox crash and 3 different computers since avast update!.
-
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.
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".
Thanks for this! After this mod, no more crashing with either ff 33.0.1 or palemoon! Hope this Avast problem is fixed soon!
-
@eapraven,
You're welcome.
-
vast2015 HTTPS scanning has bug.Avast2015 HTTPS does not work with Firefox.
Firefox won't close with Avast 2015 10.0.2206 when HTTPS scanning is enabled
(see detail https://bugzilla.mozilla.org/show_bug.cgi?id=1087674 )
Firefox cannot find addon updates with Avast 2015 10.0.2206 when HTTPS scanning is enabled
(see detail https://bugzilla.mozilla.org/show_bug.cgi?id=1088471 )
-
vast2015 HTTPS scanning has bug.Avast2015 HTTPS does not work with Firefox.
Firefox won't close with Avast 2015 10.0.2206 when HTTPS scanning is enabled
(see detail https://bugzilla.mozilla.org/show_bug.cgi?id=1087674 )
Firefox cannot find addon updates with Avast 2015 10.0.2206 when HTTPS scanning is enabled
(see detail https://bugzilla.mozilla.org/show_bug.cgi?id=1088471 )
Avast is aware of the HTTPs scanning bug, (I reported the problem on the day Avast 2015 came out.) The software that decodes and encodes the https signals is currently struggling. Avast is aware of the issue and are working on a fix.
-
And this has what to do with Firefox closes??
-
And this has what to do with Firefox closes??
HTTPS scanning in WebShield is what is causing Firefox to crash on close.
-
Hopefully this is something the mighty devs at Avast are working on!
-
I have FF 33.0 and it does not crash with Avast 2015 Free. I don't use the profile sync and I have Adblock Edge, WoT and Avast plugins installed. Not sure that will help but there we are.
-
I have FF 33.0 and it does not crash with Avast 2015 Free. I don't use the profile sync and I have Adblock Edge, WoT and Avast plugins installed. Not sure that will help but there we are.
Try "Add-on manager -> Check for (installed) updates" with "https scanning" enabled in Avast.
Then close the browser.
-
How many of those with FF crashing also use FF Sync? Would make sense that this is the cause for it. After all, its using secure connection as well.
-
How many of those with FF crashing also use FF Sync? Would make sense that this is the cause for it. After all, its using secure connection as well.
I don't use FF Sync.
-
I don't use FF Sync either -- I hadn't noticed a problem with extensions auto-updating (NoScript updated just fine last night), but I have gotten a FF crash report every time I've closed it.
Since disabling HTTPS scanning seems to be the answer for most people, I'll follow suit and hope for the best ... it seems likely that the chance of picking up malware from a secure connection is inherently quite a bit less than from a standard HTTP site. And the file shield should pick up anything that does happen to slip through.
-
I have FF 33.0 and it does not crash with Avast 2015 Free. I don't use the profile sync and I have Adblock Edge, WoT and Avast plugins installed. Not sure that will help but there we are.
Do you have Avast HTTPS scanning enabled? What OS?
-
How many of those with FF crashing also use FF Sync? Would make sense that this is the cause for it. After all, its using secure connection as well.
No Firefox Sync here. Firefox 33.0.1 will be officially released soon, but nothing is mentioned of this problem in it's release notes.
-
Firefox 33.0.1 has been officially released, no difference, crash at closing. Looking at the Mozilla bugs, the Firefox developers seem to believe it is Avast's responsibility, "It's likely an issue on their side, with DLLs hooking firefox.exe making it crash". I do hope Avast is investigating the problem.
-
I have Firefox 33.0 with WOT, ad block plus and avast plugins. It too crashes after I installed the avast plugin and not before that.
-
There appears to be some correlation between firefox after version 31 and this problem. I have gone back to a version prior to v32 and have no more close problems.
-
It has nothing to do with extensions/addon or plugins at least for me. I created a new profile meaning no addons installed, all plugins disabled. It crashes after closing 100 percent repeatable.
https://crash-stats.mozilla.com/report/index/30ace74f-15bf-41f5-8dc7-b32972141025
-
Disable HTTPS scanning, it breaks all sites for me. Uninstall avast extensions. Remove all avast plugins from browser.
Your browser should be stable now.
-
Can anyone verify if the Avast team knows about this and is working on it? In another thread, the Avast representative said they didn't know of any issues with their https scanner.
-
Well, here was my (probably first of them all) message abiout the crashing:
https://forum.avast.com/index.php?topic=157166.msg1136464#msg1136464
It seems avast! team missed it somehow...
-
Firefox 33.0.1 has been officially released, no difference, crash at closing. Looking at the Mozilla bugs, the Firefox developers seem to believe it is Avast's responsibility, "It's likely an issue on their side, with DLLs hooking firefox.exe making it crash". I do hope Avast is investigating the problem.
Thanks for the info. I'd upgraded FF to 33.0.1 and was planning to re-enable HTTPS scanning, particularly since the FF release notes mention some changes to encryption handling, to see if the conflict was fixed. But you obviously beat me to it, and sounds like there's no point trying for a while longer.
-
Take a careful look at the Firefox Crash report. I found that it referred to my AMD Video Driver 13.251. If you want to stop the activity use the Tools menu in Firefox to locate "Options-Advanced Options" and you will find the crash reporter and health reporter. UNCHECK them. This should solve the false report you get on screen after exiting Firefox.
Must add that at no time was Avast mentioned as the cause.
-
Take a careful look at the Firefox Crash report. I found that it referred to my AMD Video Driver 13.251. If you want to stop the activity use the Tools menu in Firefox to locate "Options-Advanced Options" and you will find the crash reporter and health reporter. UNCHECK them. This should solve the false report you get on screen after exiting Firefox.
Must add that at no time was Avast mentioned as the cause.
I use a Nvidia card so I don't think it has anything to do with video drivers. Also even if you suppress crash reporting, it definitely crashed b/c you can't open firefox again for a while after closing b/c there is already another instance running meaning Firefox is having trouble closing, you can see Firefox still running in the task bar manager, it only stops after it crashes b/c it can't close properly thus crashing after exiting.
-
Firefox 33.0.1 crashes on my laptop and desktop with https scanning enabled.
Once https scanning disabled, firefox exit normally.
-
I updated to 33.0.1 then updated java as there was an update.
Since then firefox has not crashed at all.
-
I updated to 33.0.1 then updated java as there was an update.
Since then firefox has not crashed at all.
I have JRE 8 U25 installed but it's not available to any of the browsers. Java is not an issue with the crashes I was having before I disabled https scanning.
-
I have JRE 8 U25 installed but it's not available to any of the browsers. Java is not an issue with the crashes I was having before I disabled https scanning.
I do not think it was java either just telling what I did.
Was crashing or Firefox.exe would not close on exit with 33 but now I am crash free even with https scanning enabled.
Perhaps it is some other plugin/extension other people have that I do not causing the crashes.
What happens in Firefox safe mode or all plugins/extensions disabled and https scanning enabled?
-
AS I stated before - the Crash Reporter indicated that my AMD/ATI R5450 video card Driver 13.251.0 was the issue. This is not the problem IMO. The problem lies with the Firefox Stub 33.0.1 and other prior editions using a stub installer. I am now testing Firefox 33.0.1 having done a very "clean" install with the Mozilla support site provided FULL version of 33.0.1.
Whether one has on-board or a separate card (like mine) for video is NOTthe problem. This is a Firefox issue. I do not consider Avast to be at fault either, tho I do turn off things I actually don't need:) As to plug-ins - all of mine are current and are not active, except for Flash Player (needed for use with games on Facebook). BTW: IE-11 does not crash at all ( I rarely use it).
If someone can verify that using the full version from Mozilla actually solves the problem - that would be very useful for all of us.
MY system uses Windows 7 64bit SP-1 Ultimate.
-
After two days with no crashes and https scanning enabled, Firefox has started crashing again or having the crash report box come up.
Back to running with https disabled.
Not sure why I had two days without any crashes.
Edit: All of my crash logs seem to point to flash player
Crash Reason: EXCEPTION_ACCESS_VIOLATION_READ
Crashing Thread: FlashPlayerPlugin_15_0_0_189.exe
-
After two days with no crashes and https scanning enabled, Firefox has started crashing again or having the crash report box come up.
Back to running with https disabled.
Not sure why I had two days without any crashes.
Edit: All of my crash logs seem to point to flash player
Crash Reason: EXCEPTION_ACCESS_VIOLATION_READ
Crashing Thread: FlashPlayerPlugin_15_0_0_189.exe
What happens when you change it's option from always active to ask ?
-
im crashing too.
-
im crashing too.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1414409946062-11774.png)
No crashes here. :)
-
No crashes here. :)
Have you visited https sites with Firefox 34 with Avast's HTTPS web scanning enabled and then closed Firefox and waited about a minute before logging off the Windows user or shutting down? Firefox hangs after close before crashing later.
Per the Bugzilla report, others are having crashes on Firefox 34 due to https scanning.
-
It's not something I've had. No crashes on closing even when I wait and use a different browser.
Firefox 34 is also extremely fast.
It is using quite a bit of Ram.
-
Quote from Bugzilla
As this is only happening with Avast, it is likely that they do something that gets our update checks from GMPInstallManager.jsm stuck or makes them throw in an unexpected place.
Just today on Bugzilla, I was asked to disable OpenH264 plugin update checks in Firefox and check for crashes with HTTPS scanning enabled. I did so and no crash.
I had to disable Add-on Update Checker as that triggers update checks on the OpenH264 plugin, which I wouldn't have thought.
Does Firefox 34 beta have this plugin? It is installed by Firefox 33 update or clean install.
-
Quote from Bugzilla
As this is only happening with Avast, it is likely that they do something that gets our update checks from GMPInstallManager.jsm stuck or makes them throw in an unexpected place.
Just today on Bugzilla, I was asked to disable OpenH264 plugin update checks in Firefox and check for crashes with HTTPS scanning enabled. I did so and no crash.
I had to disable Add-on Update Checker as that triggers update checks on the OpenH264 plugin, which I wouldn't have thought.
Does Firefox 34 beta have this plugin? It is installed by Firefox 33 update or clean install.
OpenH264 is something that Mozilla will bundle in with 34. They are focusing on trying to get the H264 protocal standerdised.
-
Believe me version 2015 freezes not only Firefox 33 but also Chrome and Opera...!!
-
@ Goher John,
I'm currently on a different computer. 33.01 crashes after closing FF.
I'm installing version 34 (Aurora) now. will let you know when it's up and running.
-
@ Goher John,
I'm currently on a different computer. 33.01 crashes after closing FF.
I'm installing version 34 (Aurora) now. will let you know when it's up and running.
It also crashes on today's Nightly build which is ver 36. The bugzilla report says version 33 - 36 is affected.
-
im crashing too.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1414409946062-11774.png)
No crashes here. :)
and???? you are on beta, you're free to test it but don't expect everybody to do it.
Believe me version 2015 freezes not only Firefox 33 but also Chrome and Opera...!!
yep, it's a pain.
-
I get browser crashes too with the new Avast 2015.
I'm surprised given the huge number of views that this thread is attracting that someone from Avast has not responded saying that they are working on the issue (or even aware of it).
In another thread, the Avast employee said they were unaware of any issue with the HTTPS scanner.
Seems like there is a lot of room for Avast to improve their communication with their customers.
-
Yes the silence is deafening from avast and firefox. I can't even find 33.0.1 on firefox site at all.
-
Yes the silence is deafening from avast and firefox. I can't even find 33.0.1 on firefox site at all.
https://bugzilla.mozilla.org/show_bug.cgi?id=1087674
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/33.0.1/
-
Believe me version 2015 freezes not only Firefox 33 but also Chrome and Opera...!!
Don't blame FF 33 or any other browser...it is a general problem caused by avast 2015...it freezes IE9 too.....!!
-
Believe me version 2015 freezes not only Firefox 33 but also Chrome and Opera...!!
Don't blame FF 33 or any other browser...it is a general problem caused by avast 2015...it freezes IE9 too.....!!
IE's current version is 11.
-
@bob, IE 9 is the last IE released for Vista, and still supported For Windows 7 until Jan 2016. However, I thought https scan wasn't included in Vista though?
-
@bob, IE 9 is the last IE released for Vista, and still supported For Windows 7 until Jan 2016. However, I thought https scan wasn't included in Vista though?
You are correct in your assumption. Can't see your computer and specs aren't listed in your signature. :)
-
Firefox 33.0.2 out now chrash fix guys? i know the issue is avast 2015 but maybe...
I uninstalled Avast 2015 last night and rolled back to Avast 2014.
-
Firefox 33.0.2 does not address the issue. Hopefully 33.0.3 will.
-
@bob, IE 9 is the last IE released for Vista, and still supported For Windows 7 until Jan 2016. However, I thought https scan wasn't included in Vista though?
You are correct in your assumption. Can't see your computer and specs aren't listed in your signature. :)
I have a Windows 8 machine. However, I bought up https scanning in Vista, b/c I assume most IE 9 consumer users are on Vista. Windows will automatically update to the latest IE version unless you tell it not to. Business turn off the update, but I assume most non business people don't bother.
So I thought Harikrishnan complaints about IE 9 wasn't relevant to this particular thread b/c I assumed he/she was on Vista. However, it I just looked at his Windows 7 signature so I guess that wasn't true.
-
@bob, IE 9 is the last IE released for Vista, and still supported For Windows 7 until Jan 2016. However, I thought https scan wasn't included in Vista though?
You are correct in your assumption. Can't see your computer and specs aren't listed in your signature. :)
I have a Windows 8 machine. However, I bought up https scanning in Vista, b/c I assume most IE 9 consumer users are on Vista. Windows will automatically update to the latest IE version unless you tell it not to. Business turn off the update, but I assume most non business people don't bother.
So I thought Harikrishnan complaints about IE 9 wasn't relevant to this particular thread b/c I assumed he/she was on Vista. However, it I just looked at his Windows 7 signature so I guess that wasn't true.
No..mine is Windows7...I haven't updated IE because I'm not using it. Yesterday I just tested it to confirm avast 2015 freezes every browser...
-
Avast 2015 isn't freezing any browsers on the many computers I manage. Strange.
My software and OS is however up to date on all of those computers. :)
-
Avast 2015 isn't freezing any browsers on the many computers I manage. Strange.
My software and OS is however up to date on all of those computers. :)
Software and OS is up to date here, but appears https is still causing crashes on close. FF executable hangs until FF forcibly closes the process. Only then does the crash notification box appear. Otherwise, FF runs fine.
But must mention that this crash on close issue has been ongoing for some time, but only once in a while, and not on a consistent basis as now. It's the https here but earlier it was something else entirely. FF has a history of doing this anyway.
-
This has become one of the most frequent crashes (maybe even the top) so Firefox developers cannot ignore it. It has to do with Open h264 plugin installed on Firefox 33 and up, and Avast hooking into Firefox to scan SSL. Why Avast did not test this before they releases Avast 2015 is beyond me. The Open h264 plugin and Firefox 33 was released before Avast 2015, and the plugin itself was in the development channels for a very long time.
" Sounds a lot like Avast is doing an SSL MITM to scan stuff and we correctly" block that due to cert pinning (correctly because when we see a cert from a wrong issuer, we should block as it easily could be a real attack)."
"(In reply to Georg Fritzsche [:gfritzsche] from comment #35)
> Jorge, can you reach out to Avast on the breakage they cause?
I'll get in touch with our known contacts."
https://bugzilla.mozilla.org/show_bug.cgi?id=1087674
-
Seems to be solved in Firefox 33.1.
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/33.1-candidates/build2/
Please report here if you still experience crashes with that build.
-
Thanks guys.
A summary of this bug:
- avast HTTPS scanning causes that all connections have valid (signed by avast root) but different certificate that is expected
- firefox uses certificate pinning to to verify the issuer of the certificate when checking extension updates
- eventhough the cert is "valid", it is not good enough to validate the extension update connection
- when firefox sees this, the task is not aborted correctly and firefox crashes during shutdown on timeout
- fixed in Firefox 33.1 - will no longer crash
- fixed in Avast via VPS - URLs used for extension update check are not scanned - should not crash with Firefox 33.0 anymore
Thanks you guys for raising this issue to both us and Mozilla.
Lukas.
-
Good to hear it will be fixed soon.
-
I cannot reproduce the problem anymore.
Thanks! Avast!
-
- fixed in Avast via VPS - URLs used for extension update check are not scanned - should not crash with Firefox 33.0 anymore
Lukas.
Thanks, without the exclusions, I'm guessing that Firefox wouldn't be able to update any extensions regardless of Mozilla's fixes to Firefox???
Seems the entire mozilla.org domain is excluded from HTTPS scanning. At least, bugzilla returns DigiCert Inc cert instead of the avast! Web/Mail Shield cert.
-
Thanks guys.
A summary of this bug:
- avast HTTPS scanning causes that all connections have valid (signed by avast root) but different certificate that is expected
- firefox uses certificate pinning to to verify the issuer of the certificate when checking extension updates
- eventhough the cert is "valid", it is not good enough to validate the extension update connection
- when firefox sees this, the task is not aborted correctly and firefox crashes during shutdown on timeout
- fixed in Firefox 33.1 - will no longer crash
- fixed in Avast via VPS - URLs used for extension update check are not scanned - should not crash with Firefox 33.0 anymore
Thanks you guys for raising this issue to both us and Mozilla.
Lukas.
Thank you for Avast.
And thanks for the info. I appreciate it.
-
Hi,
I have the same problem in my desktop pc. Firefox is crashing every time I open it and try to use it. If you open the Task Manager you can see that Firefox remain active, using resources, after it is closed. The last update from Mozilla (Fx 33.0.2) did not solve the problem.
I think that is time that Avast and Mozilla work together to solve the situation at once. It's a shame.
Windows 8.1 Pro WMC updated. Spanish. 64 bits
Avast Free 2015
Firefox 33.0.2
Windows firewall
OpenDNS servers
OpenDNS Updater 2.2.1
-
Hi,
I have the same problem in my desktop pc. Firefox is crashing every time I open it and try to use it. If you open the Task Manager you can see that Firefox remain active, using resources, after it is closed. The last update from Mozilla (Fx 33.0.2) did not solve the problem.
I think that is time that Avast and Mozilla work together to solve the situation at once. It's a shame.
Windows 8.1 Pro WMC updated. Spanish. 64 bits
Avast Free 2015
Firefox 33.0.2
Windows firewall
OpenDNS servers
OpenDNS Updater 2.2.1
Make sure your Avast VPS is up to date.
Read the reply from Avast:
https://forum.avast.com/index.php?topic=157675.msg1143777#msg1143777 (https://forum.avast.com/index.php?topic=157675.msg1143777#msg1143777)
I haven't had any crashes since the fix.
-
I realise that this is stupid question, but what is the 'VPS' ? I had a quick look through the thread and couldn't find a definition of the TLA, so thought I may as well display my ignorance.
-
I realise that this is stupid question, but what is the 'VPS' ?
They are the virus definitions or virus database. In other words, update your Avast.
-
I realise that this is stupid question, but what is the 'VPS' ?
They are the virus definitions or virus database. In other words, update your Avast.
There's two ways avast updates the virus definitions database:
- VPS update: This is the old way of updating virus protection and comes in 2 sometimes 3 times a day.
- Streaming updates: As many as 500 + updates in a 24 hour period. Since each update is very small, impact on your system is much less and you are covered against the latest threats much sooner.
Once in a while, there are no VPS updates on a given day. Not to worry, as streaming updates will always cover you and are more current than waiting for the next VPS to come in, in say, 12 hours.[/list]
-
Thanks guys.
A summary of this bug:
- avast HTTPS scanning causes that all connections have valid (signed by avast root) but different certificate that is expected
- firefox uses certificate pinning to to verify the issuer of the certificate when checking extension updates
- eventhough the cert is "valid", it is not good enough to validate the extension update connection
- when firefox sees this, the task is not aborted correctly and firefox crashes during shutdown on timeout
- fixed in Firefox 33.1 - will no longer crash
- fixed in Avast via VPS - URLs used for extension update check are not scanned - should not crash with Firefox 33.0 anymore
Thanks you guys for raising this issue to both us and Mozilla.
Lukas.
Is this the update that solves the FF33 problem...?
-
I noticed that VPS 14103101 fixed the problem for me yesterday. It may have been an earlier VPS update, but I'd turned off HTTPS scanning so wouldn't have noticed.
-
The important part isn't to nail down the update that fixed the problem.
The important part is that you, after updating, no longer have the problem. :)
-
I am running the latest version of Firefox ( 33.02 ) and the latest version of Avast Premier and Firefox is STILL crashing for me!!!!
-
I am running the latest version of Firefox ( 33.02 ) and the latest version of Avast Premier and Firefox is STILL crashing for me!!!!
Whatever the Avast guys claims about the fixing of FF33 problem, I still experience FF33 freeze and need to press the restart button to use my pc and I stands strongly on my previous post that Avast 2015 freezes every browser on some occasions. There is still something that avast team failed to identify about the browser freezing problem.
-
I am running the latest version of Firefox ( 33.02 ) and the latest version of Avast Premier and Firefox is STILL crashing for me!!!!
Whatever the Avast guys claims about the fixing of FF33 problem, I still experience FF33 freeze and need to press the restart button to use my pc and I stands strongly on my previous post that Avast 2015 freezes every browser on some occasions. There is still something that avast team failed to identify about the browser freezing problem.
Are your VPS updates up to date ???
-
I am running the latest version of Firefox ( 33.02 ) and the latest version of Avast Premier and Firefox is STILL crashing for me!!!!
You need FF 33.1..!
-
I am running the latest version of Firefox ( 33.02 ) and the latest version of Avast Premier and Firefox is STILL crashing for me!!!!
Whatever the Avast guys claims about the fixing of FF33 problem, I still experience FF33 freeze and need to press the restart button to use my pc and I stands strongly on my previous post that Avast 2015 freezes every browser on some occasions. There is still something that avast team failed to identify about the browser freezing problem.
Are your VPS updates up to date ???
Yes bob...it is 141101-0 and Asyn where is FF 33.1
-
Asyn where is FF 33.1
See: Reply #96
-
Again Chrome freezes on start up just before...!!! that's why I'm saying it is not a FF only issue...(I experience this on FF, Chrome, Opera & IE / is it happen only for me??)
-
Sorry, this topic is about Firefox, if you've problems in Chrome start your own topic.
-
Again Chrome freezes on start up just before...!!! that's why I'm saying it is not a FF only issue...(I experience this on FF, Chrome, Opera & IE / is it happen only for me??)
Please start your own topic. This thread is about Firefox. :)
-
Sorry, this topic is about Firefox, if you've problems in Chrome start your own topic.
I'm not deviating this topic to chrome but trying to convince avast guys not to focus only on FF33 and I think I have posted enough about this in this thread and not going for another here or in a new thread.. :D
-
This thread is about a specific problem with Avast 2015 and Firefox 33.0.x. That problem is now resolved. Any other problems don't relate to this thread.
-
This thread is about a specific problem with Avast 2015 and Firefox 33.0.x. That problem is now resolved. Any other problems don't relate to this thread.
Who told you it is resolved...? >:( I'm also a FF33 user with avast 2015 installed and I still experience the problem. Resolved would mean 'resolved for all'... :o
-
Who told you it is resolved...? >:( I'm also a FF33 user with avast 2015 installed and I still experience the problem. Resolved would mean 'resolved for all'... :o
Resolved in 33.1 and beyond not 33.0.2 which is what you most likely have.
Read: https://forum.avast.com/index.php?topic=157675.msg1143777#msg1143777
Download: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/33.1-candidates/build2/
-
Though the exclusion in VPS already seems to partially help. I'm not getting this anymore on my laptop where i got the crashes most often. But will fully be fixed with 33.1 i guess.
-
This thread is about a specific problem with Avast 2015 and Firefox 33.0.x. That problem is now resolved. Any other problems don't relate to this thread.
Who told you it is resolved...? >:( I'm also a FF33 user with avast 2015 installed and I still experience the problem. Resolved would mean 'resolved for all'... :o
You have another problem (no idea what) causing your crashes. I never said that anything was fixed for all people having other problems with Firefox.
The VPS update definitely fixed the problem people were having with Firefox crashing on close due to extension updates check. FWIW, I've never had a crash with Opera nor Internet Explorer.