Search button causes CPU usage to 95+%!

I'm using DO 8.2.2.3: While using the "Commander" (two side-by-side panes) Lister Style and I select FILE/FIND, the pop-up window "Find - Directory Opus" appears... In the top input-box that allows for the designation of the desired directory/sub-directory to search, there are two buttons to the immidate right... the first to pop-up a window to select the directory, the second to pop-up a window to select the Hard Drive...

If I press that first button (to select the directory), the next pop-up window appears "Select Folder"... my HD light flashes a bit (stops after about 10 seconds)... the hour glass (wait) icon appears... but the wait expires my patience (so far about 120 seconds), and during this whole time, the D.O.'s executable usage averages about 95% of my available CPU time... effectively slowing everything down on my PC to a crawl. The only escape is to kill the DO process via the OS.

I've another problem with this find command (when I carefully avoid the above trouble): Once I kick-off a find command to search through a considerable directory/sub-directory hierarchy... the process appears to quickly look through 5-10 sub-directories, then stop prematurely - reporting no success. The erroneous speed that it completes the search (too quick) is obviously wrong... and I can see the few sub-directories that are actually searched.

I didn't experience this problem using any of the previously available releases. As far as my PC is concerned, these are new "release related" application bugs.

The first problem sounds like there's a drive on your system which is causing a problem.

Does a similar thing happen if you open Internet Explorer, go to Tools -> Options -> General -> Temporary Internet Files -> Settings and click Move Folder... to display the standard folder picker? If so the problem isn't Opus-specific. If not then try running FileMon in the background to see which paths Opus seems to be accessing when the problem occurs.

The second problem sounds like you've either defined a search filter which excludes certain directories (i.e. you're using the Advanced tab and haven't cleared out an old filter) or the account you're running under doesn't have access to some of the directories you're expecting to search. Or the filesystem has cached the directory information and is returning much faster than you expect it to, which happens if you do a couple of searches in a row, for example.

Hi nudel:

Your recommendation about checking things out via using Internet Explorer suggested the trouble WAS with DO: the problem could not be duplicated using your above recommended alternative.

This got me to thinking further on the idea of testing a "parallel" application though... so I shut down DO, and fired up MS's own "Windows Explorer"... when I navigated down to this same troublesome directory, explorer had trouble with it too... like DO, when I attempted to open this directory via clicking on it's text-title, explorer displayed the hour glass, my disk activity stopped in about 10 seconds, and the application was reported as consumming 96% of my cpu's time...

So... OK... this problem then IS NOT D.O. specific.

FYI... This problem still surfaces, though only with one particular directory (under the root). Using either explorer or DO, if I click on the left image icon next to the directory name (the "+" in explorer, an image of a folder in DO), the directory expands correctly: I can then further navigate within the lower directories/files... It's only if I click on the directory name itself (again, in either explorer or DO), that the hour glass appears, and the cpu usage approaches an uncontrolled 95+%. FileMon shows huge disk IO (with either app) that's beyond my ability to understand.

The "File/Find" issue resolved itself... I removed and reinstalled the latest three releases of D.O. over the past day or two - trying to troubleshoot my issues... looking to see if these problems were release related... they weren't... I replicated both problems to each of the last three releases... the directory listing problem turned out to be elsewhere within my PC (still undetermined)... and the File/Find function is now working correctly...

I'll look elsewhere for help with this odd dirctory problem (I'm still experiencing)... in the meantime, I've narrowed down what triggers the run-away condition... so I'll just avoid tripping it off - doing the (not-too-much-trouble) work around...

Thanks for your help !

D.O. is great... someday I'll quit work and leave my dog & family behind... go off to some remote island... and finally invest the necessary time & energy to figure out all the available D.O. options/customizations, etc... In the meantime... I just look at all the sub-menus and dream of the day in my distant future when I may get a chance to play with all of these neat options!!

Good to know neither problem was caused by Opus, at least. Hope you find a solution.