Dissconnecting Problem
 

I'm afraid Frostwire is not behaving perfectly. I have done one overnight session with it and next morning it was working, but had evidently been disconnected at some stage as it was showing a message that it was disconnected, and would continue to try to re-connect.

To day, I had it running for about 6 hours and found it dissconnected with the error notice as above. ( on both occasions DSL connection still running)

It was a matter of urgency to get onto e-bay and everything on the computer had slowed to a total crawl (if that). I had to crash close the computer, but missed the auction all the same.:( So I cannot give you too many details ... Only that this seems to be a big problem, at least with my set up

Aditional details: 400 Mhz power pc processor Memory 320 MB Free Space on Start up disc. 9.5GB Sharing 2,500 files ... no downloads in this session

Hobo, I noticed the disconnect message a few times when I was away from the computer this week, but FW had switched to Ultrapeer from leaf during the same time.

I'm trying to find out if the new code that decides Ultrapeer might be the problem, and wonder if maybe yours was attempting to switch to UP too.

the problem may be caused by certain different command-line options, we may be using for frostwire

also got that problem -- may explain why I'm more quickly an UP with FW than with the equivalent LW.

Ciao

The ultrapeer switching sounds possible. I have yet to find Frostwire in Ultrapeer mode, but Limewire 4.9.29 is almost always running as ultrapeer despite my fairly low dsl connection.

If this happens again I shall dissable ultapeer and see if it still happens.

Last night same problem ..was connected as a leaf ..disconnected at some stage of the night ... This morning was connected as an ultrapeer. Tonight I shall try it with Ultrapeer capabilities swithed off.

I ran last night with ultrapeer capabilities dissabled, but found that the message on disconnecting, but trying to reconnect was showing again. An upload was taking place but evidently I disturbed something bringing the display back to life as two ultrapeers connected the moment I did this. The CPU shot up to about 75% just after this but settled down after a few minutes.

Hi Hobo--nice info.

So, it now looks like it is related to the " Idle Connection bug on LimeWire 4.9.30" that many Cabos users are reporting too.

(It happened again here last night, but I didn't have UP disabled. Doesn't look like the uploads were affected.)

Stief I agree the uploads carry on well ... I haven't been doing any big downloads ... can't find or think of anything I want to get right now! but I'm suspecting that downloads will be kicked into "need more sources" mode which will effectively stop them . That is unconfirmed .. just a guess.

FW 4.9.34 went to UP last night, and no disconnect message this morning. Good--the switch to UP is not the sole factor (or has been fixed, I know not how ;) )