This isn't the case for me, since I can quit Phex, and go back in to it and it makes connections instantly. Therefore no blocking is taking place.

Actually I've also noticed that when I first run Phex, in the middle of the "Gnutella Net" screen it says: My Address 127.0.0.1:3617, then Phex tries to connect to about 5 other hosts, they all sit there "connecting" until My Address changes to my "Internet IP" then instantly the 5 hosts change to "Outgoing" and connections are made. After several hours, all of a sudden My Address changes back to 127.0.0.1:3617 and no more connections or downloads can happen afterwards, and Phex can no longer connect to more hosts so they slower drop off. I'm trying to find a relation between this weird IP address thing and the problem with 1000's of Phex processes.

I'm currently at 1011 processes and my IP address in Phex just changed to 127.0.0.1 while I wrote this. Could it be Phex's way of limiting the processes? Once too many are spawned it changes the IP address in an attempt to bring the processes down? Though I've never had it recover after about 500 processes. My Phex uptime is only 20mins.

Hi...

could you please explain me better what you mean with >1000 processes?
What OS are you using? How do you determine the number of processes Phex is using? Can you send me screenshots?

There should be no relating I know between so called 'processes' and the IP.

Gregor

__________________

I think i've got kinda the same problem. 127.0.0.1 ( localhost ) is listed as my IP adress. I explicity changed it to my actual (outside world internet ) IP adress, my local address, and several other adresses just for the hell of it.

No matter what it's listed as, Autoconnect still won't try and connect me to any sites in the host catcher.

On the plus side, i can still connect to sites manually by clicking on a host catcher IP and hitting connect, but it's a tedious process getting a solid connection.

I can still get a list of sites from a host to fill the catcher up too. Just seems like that little checkbox for auto connect doesn't seem to realize it's checked.

I had phex running quite well, was impressed with the whole gamut and was very much converted from limewire up until this happened. Had an uptime of several hours, and now no amount of quitting or rebooting seems to fix it.

I didn't notice any extra processes running, but them i'm Running OS X so maybe it's not handled the same.

My OS is Windows XP with J2SDK 1.4 and there is also the problem with the own IP address 127.0.0.1. The first time I used Phex the IP was right but after quit and a 2nd start Phex always uses 127.0.0.1.
Then it seems to be in an endless loop. I can choose the disconnect menu but nothing happens.

Okay, the thing I miss most from earlier versions from Phex is the ability to highlight multiple search results at once (using CTRL or SHIFT) and then hit "download" (or "quick download") once to transfer ALL of them to the download list. Now that only transfers the first one selected, making trying to download a large number of files at once a very tedious process indeed. Could this functionality be brought back in future versions, please?

As for the big problem, Phex constantly crashes on me now. I tried running the debugger but that gave me no useful information whatsoever before locking up. I have not yet been able to determine what causes the crashes, but I never used to have this many lockups with previous versions...

Thanks for listening.

Jonathan Hagn
jhagn@mindspring.com