workaround for GUI-freeze-bug
 

Many users complained about a nasty bug of the GUI (graphical user interface). The user interface freezes when there are many results of a search.

I think I found a workaround for this:

Set the search-result limit to a huge number (like 8000).

I appears that the freezing occurs when the limit is reached so the obvious solution is to avoid this condition. I tried this for some time and Phex didn´t crash although I did a lot of popular searches.

I hope this solves this issue for now and makes Phex a lot more usable for you.

Cool - it seems to work!
 

Sometimes solutions can be so easy....
well, at least it works so far, even with hundreds of returned results.
I'm always surprised how many people are not using Phex yet.....once you tried it, you never want to use anything else anymore.

Danke und weiter so! :)

Works great for me
 

Awesome! Fixed the freezing completely... Thanks Konrad

Where can I change the search-result limit?

The thread was 5!!! years old...

I think we have rewritten the search interface code about 4 times since then...

The option is not available anymore... Why would you like to set a search result limit? There should be no need to do this...

Ok, but I'm running 2.8.4.93, and this interface is still EXTREMELY slow compared to Limewire or Frostwire. Download speeds are comparable, but the program runs excruciatingly slow. Especially when there's a large number of search results being displayed.

Any fix for this in the current version?

I think limewire limits the search results displayed at a certain limit...
we could do this too... have you tried stopping the search early when you received enough results?
Though I have to say that I never experienced extrem slow downs on my 1,5GHz on Windows.

That might be the problem... I've noticed I'm getting MANY more search results than Limewire. I don't want to limit the results, because I'm looking for an old file that's proving hard to find, but it's name is made up of common words, so I get all kinds of results that aren't relevant. It would suck to stop the returns before the real file showed up.

I'll try it again after a reboot later when I have time. It doesn't lock up or anything, you just have to let it be until it completes a search. Thinking about it, I've been doing a bunch of photo work tonight so my system is probably bogged down anyway... I'll bet a reboot helps.

You can try to limit the mass by using the quick filters. Often it helps to reduce results if you know the extension, media type or files with a size out of range.
The filters are none destructive so you can always go back to display the full results again.