Previously related view was particularly bad about exacerbating this
problem ... I did a bunch of work to try and make sure we weren't
leaking resources there, which seems to have made it better for me. I
don't know what build that went into, but you might try updating and
see if you are better off with a newer one.
ms
On May 30, 2008, at 5:06 PM, Thomas wrote:
> Wow. Thanks for the heads-up. I just checked Eclipse, debugging my
> app, and it was using over 3600 ports. I restarted Eclipse, and it
> immediately went to 2400. Launched the app again and it's at 2520.
> I'll keep an eye on it.
>
> Perhaps I should re-install a clean version of Eclipse. This one has
> been upgraded many times.
>
> Regards
> Thomas
>
> On 31/05/2008, at 6:49 AM, Mike Schrag wrote:
>
>>> * has anybody else seen this problem? MacBook Pro with (then)
>>> 10.5.2 and WO 5.4.1; with gradually increasing frequency,
>>> eventually up to once an hour, the entire user interface freezes
>>> with the death beachball, although Eclipse is still serving the WO
>>> application I am debugging. Only option is a hard reboot. I then
>>> upgrade to the latest nightly of WOLips, and the problem goes
>>> away, then comes back after a week or so and the cycle repeats.
>>> Yes, I've done the full hardware test, and the computer is fine.
>> This is probably https://bugs.eclipse.org/bugs/show_bug.cgi?
>> id=141929 if I had to take a guess. You can check the number of
>> ports Eclipse is using in Activity Monitor.
>
This archive was generated by hypermail 2.0.0 : Fri May 30 2008 - 17:17:49 EDT