Author Topic: [Bug report?] farr - short freeze every 6 launch/close (Read 88,132 times)

jgpaiva · « **Reply #50 on:** January 21, 2008, 10:45 AM »

Crazy... And i wonder why do people say comodo is a good firewall

Lashiec · « **Reply #51 on:** January 21, 2008, 07:32 PM »

Summary: I think I won't even bother about trying Comodo

. And maybe not even another 3rd party firewall

Armando · « **Reply #52 on:** January 21, 2008, 08:20 PM »

Well, I'm still using it, but I won't even *look* at the defense+ option anymore.

I might look for another firewall in a few weeks, but I don't want to mess with my computer to much right now. Firewalls and antivirus just have that potential to break everything.

J-Mac · « **Reply #53 on:** January 22, 2008, 07:51 PM »

Hmm. I ran the inireader and it took 87.29 seconds. NOD32 running, no SW firewall. However I had the task manager window open and didn't see NOD32 at all.

Tried a second time and it took 359.62 this time! Ouch! Where is the output file?

Thanks

Jim

J-Mac · « **Reply #54 on:** January 22, 2008, 07:52 PM »

Never mind - found it. 168 kb.

J-Mac · « **Reply #55 on:** January 22, 2008, 07:54 PM »

I tried Comodo about a year ago when it was in beta. Uninstalled it pretty quickly, too. It wasn't intuitive at all. Locked out my own network by default and after about a dozen attempts to get it included, it was still kicking it around. I never did like it.

Jim

J-Mac · « **Reply #56 on:** January 22, 2008, 07:55 PM »

Ouch!! Third test: 677 seconds! Getting worse!

Armando · « **Reply #57 on:** January 22, 2008, 08:07 PM »

Quote from: J-Mac on January 22, 2008, 07:55 PM

Ouch!! Third test: 677 seconds! Getting worse!

You have to disable scanning for ini files in AMON.

J-Mac · « **Reply #58 on:** January 22, 2008, 08:21 PM »

21.92 seconds after disabling INI monitoring as per Armando's post above!

Jim

f0dder · « **Reply #59 on:** June 15, 2008, 04:06 PM »

Hmm, here's a wild guess - I haven't traced the issue or anything, so it's just that - a guess. Here goes... when using traditional INI file routines, is the file opened and close for every write operation done? That could explain why it's slow, and why nod32 slows it down even more...

Armando · « **Reply #60 on:** June 16, 2008, 02:02 AM »

Just to mention : when farr writes change to the ini file, it's still pretty slow.

Lashiec · « **Reply #61 on:** June 16, 2008, 03:31 PM »

Quote from: Armando on June 16, 2008, 02:02 AM

Just to mention : when farr writes change to the ini file, it's still pretty slow.

Don't worry, the suffering will soon be over

Armando · « **Reply #62 on:** June 16, 2008, 04:20 PM »

Nice, thanks Lashiec.

kartal · « **Reply #63 on:** June 16, 2008, 07:39 PM »

I have alot of hit and misses as well. Sometimes Farr finds the file less than a sec sometimes it takes a long search to find the file. I am talking about frequently used programs. I even set history hit scoring to 500

Armando · « **Reply #64 on:** June 16, 2008, 07:44 PM »

Same thing here. I still haven't figured out why or when does it do that. But this is most probably a different problem altogether.

kartal · « **Reply #65 on:** June 16, 2008, 08:06 PM »

Well it is little connected because when Farr gets into deep search mode (when it cannot bring the file in a few seconds) it locks up. It is mostly an interface freezing I believe . And escape would not help me at all.

Armando · « **Reply #66 on:** June 16, 2008, 10:22 PM »

But you do get results in the mean time... But not the expected one... Right?

kartal · « **Reply #67 on:** June 16, 2008, 10:29 PM »

yes it keeps listing results but it takes a while until it makes sense of what is coming out of search. I am searching 6 7 big folders so to me searching does not bother but
I get frustrated when it cannot find frequently used and called(via Farr) applications asap.

Armando · « **Reply #68 on:** June 16, 2008, 10:41 PM »

Ok, so yes, what you're describing is exactly what's happening to me too. Has anybody else mentioned that before?

mouser · « **Reply #69 on:** June 25, 2008, 10:09 PM »

I'd love to get a report on whether the new version (2.12.03) still suffers from this problem.

Armando · « **Reply #70 on:** June 25, 2008, 11:28 PM »

Hi mouser,
It might be too early to tell for sure since I've just installed the update. But it seems to be much much better : I only get a 0.7s pause after the 6th launch/close. So that's pretty good. Also, the problem with "recently launched files not appearing at the top of the list" seems to be gone too.