I jealous Hobo I haven't been home since it came out so I haven't even been to try to break it.

Bad luck Grandpa:)

Well I did manage to break it last night ... It disconnected after 15 hours or so, but my internet connection closed as well, so either FW did not reconnect and after a period of idleness my internet connecrion closed or my internet connection closed first, which is not anything that happenned before.
Real memroy use by FW had gone up to 1.3 GB and it was not easty to restart it .. fairly well frozen..

the memory leak on OSX is well known and so far we don't have a solution for it. We will probably have to wait for Apple to fix their java implementation.

Hobo, just to make sure . . . I assume you meant that the Virtual Memory (not real memory) went up over 1.3 GB

I thought I better add that I have run FW for another long stint ... about 24 hours and it behaved excellently .. so perhaps my last problem was my isp disconnecting as they seem to be having one or two problems of late:(

The code for frostwire beta has only fundamental GUI changes at the moment.

I deleted all three peers in the connections pane and the "it appears your machine . . . . is disconnected" dialog popped up. I was still connected.

I tried again, but couldn't repeat (because of incoming search results?)

Tried again with no tranfers in progress, but FW switched to Ultrapeer. heh.

Anyway, would a check that pings "the internet" before showing the "disconnected" message prevent at least one case of a false trigger?