Avast WEBforum

Consumer Products => Avast Mac Security => Topic started by: aqi0796 on December 18, 2011, 02:54:58 PM

Title: BUG:Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash
Post by: aqi0796 on December 18, 2011, 02:54:58 PM
OS: Mac OS X Lion( 10.7.2 )
Application: Firefox 8.0.1( Down ThemAll Plugin )

My downloads sometimes stall at 99%, and Firefox crash... :(
But after I close Filesystem Shield,The App( Down ThemAll ) had returned to normal.
Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash.
Title: Re: BUG:Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash
Post by: aqi0796 on December 18, 2011, 04:33:04 PM
Another:
Web Shield cause Several ports (8080) required by Tomcat v7.0 Server at localhost are already in use. 
Title: Re: BUG:Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash
Post by: tumic on December 19, 2011, 11:05:39 AM
Another:
Web Shield cause Several ports (8080) required by Tomcat v7.0 Server at localhost are already in use. 

This is not a bug, the webshield proxy just uses that port by default (like Tomcat does) but can be configured to run on another port (like Tomcat can). See the Web Shield Proxy Default Port 8080 Not A Good Choice thread (http://forum.avast.com/index.php?topic=90129.0 (http://forum.avast.com/index.php?topic=90129.0)) for details.
Title: Re: BUG:Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash
Post by: aqi0796 on December 19, 2011, 03:45:01 PM
Another:
Web Shield cause Several ports (8080) required by Tomcat v7.0 Server at localhost are already in use. 

This is not a bug, the webshield proxy just uses that port by default (like Tomcat does) but can be configured to run on another port (like Tomcat can). See the Web Shield Proxy Default Port 8080 Not A Good Choice thread (http://forum.avast.com/index.php?topic=90129.0 (http://forum.avast.com/index.php?topic=90129.0)) for details.

Thank you. I'll try again.
Title: Re: BUG:Filesystem Shield cause Firefox's Plugin(Down ThemAll) crash
Post by: aqi0796 on December 19, 2011, 04:39:47 PM
Another:
Web Shield cause Several ports (8080) required by Tomcat v7.0 Server at localhost are already in use. 

This is not a bug, the webshield proxy just uses that port by default (like Tomcat does) but can be configured to run on another port (like Tomcat can). See the Web Shield Proxy Default Port 8080 Not A Good Choice thread (http://forum.avast.com/index.php?topic=90129.0 (http://forum.avast.com/index.php?topic=90129.0)) for details.

[http]
SOCKET="/Library/Application Support/Avast/socket.web"
LIMIT=4194304
ENABLED=0
PORT=8666--->i change the setup of Http Port
IPV6=1

Things are right now again.