Welcome Guest.   Make a donation to an author on the site October 25, 2014, 02:51:36 AM  *

Please login or register.
Or did you miss your validation email?


Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.


You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
 
Read the Practical Guide to DonationCoder.com Forum Search Features
   
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Freezing on search :(  (Read 6152 times)
jpprater
Supporting Member
**
Posts: 88



see users location on a map View Profile Give some DonationCredits to this forum member
« on: January 11, 2010, 08:25:04 AM »

FARR seems to freeze during search.  The FARR window pops up normally when I hit my hotkey, but after the first character, FARR freezes for about 5 seconds.  It does this on every search.
If this were my web browser, I'd clear the temp files...is there something like this that I should be doing every so often in FARR?  What else should I try to speed things up?  Everything else on my machine seems to be running normally.  I'm using FARR 2.80.02.

Jon
Logged
mouser
First Author
Administrator
*****
Posts: 33,590



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #1 on: January 11, 2010, 08:31:05 AM »

This has been known to happen when search network shares.. can you check your launch history and see if anything is on a network -- maybe clear it to confirm that's not it.  You can also try disabling plugins to see if that's the cause.  Another trick is to enable the option to show subdirectories names during search, and pay attention to the status bar, see what it says it is searching when it hangs.
Logged
jpprater
Supporting Member
**
Posts: 88



see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #2 on: January 11, 2010, 08:46:02 AM »

This has been known to happen when search network shares.. can you check your launch history and see if anything is on a network -- maybe clear it to confirm that's not it.  You can also try disabling plugins to see if that's the cause.  Another trick is to enable the option to show subdirectories names during search, and pay attention to the status bar, see what it says it is searching when it hangs.
It was launch history.  I cleared my launch history and that did it.  Thanks! thumbs up
When you say network shares, does that include network drives (e.g. an H drive that's mapped to a network path), or just UNC shares (e.g. \\server\sharepath)?  Because prior to seeing any slowness, I had just used the run alias to open a UNC share.  The slowness started after that, but the entry for that launch wasn't in my history.
Logged
mouser
First Author
Administrator
*****
Posts: 33,590



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #3 on: January 11, 2010, 08:51:39 AM »

Could be either.. BUT FARR tries to be smart and not resolve the UNC shares, so it probably was not that.  the network path definitely could have done it.

Since it was clearing your launch history that did it, this confirms that i probably need to have a way for farr to figure out which drives are network drives and shouldnt have their shortcuts resolved, or else allow a manual specification of such drives.
Logged
jpprater
Supporting Member
**
Posts: 88



see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #4 on: January 11, 2010, 09:19:16 AM »

Could be either.. BUT FARR tries to be smart and not resolve the UNC shares, so it probably was not that.  the network path definitely could have done it.

Since it was clearing your launch history that did it, this confirms that i probably need to have a way for farr to figure out which drives are network drives and shouldnt have their shortcuts resolved, or else allow a manual specification of such drives.
Putting a list of those drives in Options might be best, performance-wise.
I don't know how you'd check which drives are network drives via C++ or another .Net language, but I do know that you can query through WMI for that information.  Of course, you may not want to use that method because WMI can be slow sometimes.  If you want to try it, though, you'd use the following WMI query:
Formatted for SQL with the GeSHI Syntax Highlighter [copy or print]
  1. SELECT * FROM Win32_LogicalDisk WHERE DriveType=4
Win32_LogicalDisk is the WMI class representing drives on a computer, and where that class's DriveType attribute is 4, that drive is a network drive.
Logged
mouser
First Author
Administrator
*****
Posts: 33,590



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #5 on: January 11, 2010, 09:35:17 AM »

Thanks for the tips!
Logged
jpprater
Supporting Member
**
Posts: 88



see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #6 on: January 11, 2010, 09:38:07 AM »

You're welcome. smiley
[EDIT] This might be of use...
« Last Edit: January 11, 2010, 09:48:30 AM by jpprater » Logged
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
 
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.03s | Server load: 0.05 ]