Shareaza

Hi,

This same issue had also occurred in past years on another XP computer...

I installed the latest version of Shareaza (2.5.5.0) from the shareaza.sourceforge.net home page on this Dell Dimension 2400 computer a few weeks ago (I had installed a new Hard Drive back in April) and all was fine until this morning when I attempted to open Shareaza and the progress bar on the bottom of the GUI stopped at about 75% and the program failed to open. A check of the Task Manager indicated Shareaza was "not responding". A reboot of the computer failed to fix it.

I did a clean uninstall/reinstall (rebooting and scanning with CCleaner in-between) and all was well for a few hours and, after closing Shareaza and then trying to start it again, the same thing happened...GUI freezes and Shareaza is unresponsive, necessitating me to use the Task Manager (Processes) to "End Process". Also, I see that the CPU Usage is at 100% until I close Shareaza and it goes back to around zero or slightly above depending on what is running at the time.

I can do another uninstall/reinstall, reset all the settings, and probably get it working again but, what is the root cause of this ongoing annoyance (file corruption?) and what can I do to prevent it from happening in the future?

Thanks for any help!

Well, the only times where I do notice such long startup times is when I have had one or more searches opened on shutdown. The problem is it takes quite long to load searches saved to disk into Shareaza again...

I agree we should make that information more public and I have already made a suggestion for how to do it on our dev board.

As for the results, I am waiting for them.

I'm having some problem with compiling Shareaza lately, but once I have solved this I will continue some work I have been doing on search filtering. I might also have a look into the saving to and loading from file of searches - but I am making no promises here

Doesn't sound like a save/load problem to me, more like Shareaza taking a long time to rebuild the list shown in the search tab/window.

That makes sense, but wouldn't that mean that there would be a wait of several minutes every time the hits get re-filtered due to a change in the filters or security rules?

Well, in some cases this can really happen. Sometimes when there are several searches opened (as in the case that has been reported here), with complex filtering in place and a security rule is added to the list, the amount of work Shareaza has to perform can take times > 5min to completion.