Ever since I installed Comodo firefox randomly stops working. By stop working I mean it suddenly will not even time out a web page. It simply loads the page forever showing just a white page. To cure the problem I have to close firefox and reopen it.
How can i fix this aside form restarting firefox every 10 minutes or so?
Thanks!
Does this happen on every page you try to visit or just specific ones? In IE as well or only FF? See my post in this forum on Comodo doing weird things: https://forums.comodo.com/index.php/topic,8199.0.html
Probably not related but you never can tell…
I get the impression (from other problems I have, relating more to McAfee) that FF is a bit too finely tuned - sometimes it’s too fast for the server, especially if any packet fragmentation is going on.
DN
Similar problem but I have not tested in IE. Also I am only running Comodo anti-virus and firewall but have a few other installed). Nor am I using a mcafee in anyway.
As you suggested dump Mcaffe.
Xplorer4x4,
If Comodo FW is blocking your browser, there should be a log entry. Please do the following:
Go to Activity/Logs. Right-click and select “Clear all Logs.” Then open FF, and keep browsing until you get this scenario to occur. Make a note of the time.
Go to Activity/Logs. Right-click and select “Export to HTML.” Save the file, and reopen it.
Highlight the entries surrounding the time of the incident. Copy the highlighted section, then Paste into your next post here. You may edit out your personal/external IP address for privacy with “x.”
LM
Ok the lof cfp.html was from before i went to sleep and when i woke up. However cfp-small.html is taken after a period of not using firefox for a moment, firefox loading fine, and allowing me to browse for like 5 minutes. Then dieing on me. It does seem as though IE does work.
http://www.mediafire.com/?3gzwnmymz0m
http://www.mediafire.com/?0mwetkdwgqt
The HTML logs saved as text are very difficult to read, I’m afraid. If you want to upload the whole HTML file, you can use the filehosting. My preferred method is per the instructions I gave in my previous post, to simply Highlight the entries, Copy them to the clipboard, and Paste it into your post. It will come out as editable text in the same format/layout as the HTML log file.
That will make it a lot easier to identify what’s going on.
Thanks,
LM
I tried to use the attachment feature but firefox wouldnt let me. Plus “Allowed file types: txt, doc, pdf, jpg, gif, mpg, png, zip, mp3, rar” so html files are not allowed. Which was probably the reason for an error.
As for the logs couldn’t you just convert them back to HTML files. 
I have had to disable comodo av and firewall(via task manager at boot up) because a) it was causing lots of lock ups on my PC that were only fixable by powering off and powering back on. I could not reset via task manager or gain access to the start menu. The lock up usually ocurs when I try to launch a program via quick launch icon. Such activity could have only been traced down to the comodo apps or my trillan alpa version. I have been running Trillan Alpha for hours with out such issues above so this single it out to comodos apps. Seeing as I did nto have the issues with comodo firewall i think it is comodo firewall.
Resources should not be an issue. In short I have a P4 running 1.25 gb of ram.
That’s why the copy & paste into your post, instead of attaching… You can attach a zip or txt file, but there is a size limit (which the full log would exceed).
I could, yes, and I have. I prefer that the user do so, to make better use of my volunteer time… 
The small log has nothing to do with Firefox not working properly. These entries from the full log do:
Date/Time :2007-04-23 20:11:24
Severity :Medium
Reporter :Application Monitor
Description: Application Access Denied (firefox.exe:85.17.143.79: :http(80))
Application: C:\Program Files\Gran Paradiso\firefox.exe
Parent: C:\WINDOWS\explorer.exe
Protocol: TCP Out
Destination: 85.17.143.79::http(80)
Date/Time :2007-04-23 20:11:24
Severity :Medium
Reporter :Application Monitor
Description: Application Access Denied (firefox.exe:192.168.0.1: :dns(53))
Application: C:\Program Files\Gran Paradiso\firefox.exe
Parent: C:\WINDOWS\explorer.exe
Protocol: UDP Out
Destination: 192.168.0.1::dns(53)
Date/Time :2007-04-23 20:11:19
Severity :Medium
Reporter :Application Monitor
Description: Application Access Denied (firefox.exe:192.168.0.1: :dns(53))
Application: C:\Program Files\Gran Paradiso\firefox.exe
Parent: C:\WINDOWS\explorer.exe
Protocol: UDP Out
Destination: 192.168.0.1::dns(53)
Date/Time :2007-04-23 20:11:18
Severity :Medium
Reporter :Application Monitor
Description: Application Access Denied (firefox.exe:127.0.0.1: :4020)
Application: C:\Program Files\Gran Paradiso\firefox.exe
Parent: C:\WINDOWS\explorer.exe
Protocol: TCP Out
Destination: 127.0.0.1::4020
Date/Time :2007-04-23 20:11:14
Severity :Medium
Reporter :Application Monitor
Description: Application Access Denied (firefox.exe:192.168.0.1: :dns(53))
Application: C:\Program Files\Gran Paradiso\firefox.exe
Parent: C:\WINDOWS\explorer.exe
Protocol: UDP Out
Destination: 192.168.0.1::dns(53)
And there’s more where that came from… 
Here’s what it looks like: When you open FF, it tries to verify your connectivity (the DNS port 53 access), but it’s been blocked from doing so. It tries to communicate via the localhost (loopback on 127.0.0.1), but it’s been blocked from doing so. It tries to connect to the internet/website (the port 80 access), but it’s been blocked from doing so (possibly because the DNS verification was previously blocked).
It is possible, given the scenario, that you are blocking svchost.exe from making the DNS connection for the system; this would cause the applications like FF to verify it themselves.
Please do the following:
If you are not using a proxy for your browsing, you may safely disable loopback monitoring - you may do so under Security/Advanced/Miscellaneous and check the boxes “Skip loopback UDP/TCP…”. OK. Firefox uses this to communicate internally; if you choose not to skip the loopbacks, you will likely need to create an additional rule for FF to use the loopback on localhost.
Also, open your Application Monitor, and look for Block entries on FF and svchost.exe. If you don’t wish svchost to connect, that’s fine; just be aware you will need to allow FF more access than you currently have. Remove any block rules for FF, and reboot. If you don’t have any block rules, reboot anyway, to clear the memory of any temporary blocks.
Click Allow with “Remember” selected, on any FF popups for the loopback, DNS, and port 80 (destination port for browsing).
LM
Once I allowed svchost all was good, untill today, it randomly stoped working again. I atached the log in html file enclosed in a rar as the forums said my message body was mepy if i posted it here
[attachment deleted by admin]
Tnx, Xplorer4x4
There are two types of entries I see in there. One (the predominant one) is blocked outgoing ICMP Port Unreachables, to a multitude of different IP addresses.
The other three are these:
Date/Time :2007-04-26 09:26:54
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 192.168.1.102, Port = nbname(137))
Protocol: UDP Incoming
Source: 192.168.1.102:nbname(137)
Destination: 192.168.1.255:nbname(137)
Reason: Network Control Rule ID = 6
Date/Time :2007-04-26 09:26:49
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 192.168.1.102, Port = nbname(137))
Protocol: UDP Incoming
Source: 192.168.1.102:nbname(137)
Destination: 192.168.1.255:nbname(137)
Reason: Network Control Rule ID = 6
Date/Time :2007-04-26 09:26:49
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 192.168.1.102, Port = nbdgram(138))
Protocol: UDP Incoming
Source: 192.168.1.102:nbdgram(138)
Destination: 192.168.1.255:nbdgram(138)
Reason: Network Control Rule ID = 6
If the ICMP was to your ISP, I’d take that on first. Since it’s not, I’m skeptical of that being the issue. However, I have read that there is a scenario in which the system will potentially use ports 137 & 138 for DNS or DHCP. So we’ll take that on first.
Go to Rule ID 6. Right-click and select Add/Add Before. Create the rule as follows:
Action: Allow
Protocol: UDP
Direction: In
Source IP: 192.168.1.102 (this is most likely your router, serving as DNS or DHCP server)
Destination IP: Any
Source Port: Any
Dsetination Port: A set of Ports: 137,138 (no space after the comma).
OK.
Then go to Activity/Logs. Right-click and select “Clear all logs.” This by itself won’t help; it’s just so we start fresh.
See how that works.
LM
Sorry I could not update sooner, but I did reboot my computer, and all is fine now. ???
Thanks again for your help Little Mac it is very much appreciated!
Well, okay then. (:TNG) We’ll consider this one resolved, and I’ll close it out. If your problem resurfaces, just PM a Moderator (please include a link), and we’ll gladly reopen it for you.
LM