Rick Genter wrote:
I looked at the output of "top"; other than eating up a ton of VM, there
doesn't seem to be any good reason for it. With my setup I usually have
close to 1GB of physical RAM free even running Eclipse, iTunes, Safari,
Mail.app and BOINC running a couple of apps. I suspect something in SWT
locks something for longer than it should (how's that for a concrete
diagnosis :-).
Try using 'top' to watch I/O (disk) activity during the audio breakups. If
memory constraints or swapping isn't a probable cause (as indicated by 1 GB
free), then contested I/O may be.
An experiment is to run Eclipse using incremental GC, and see if anything
changes. Here's how to make NetBeans use Mark&Sweep GC, from which you can
extrapolate the changes to Eclipse:
<http://weblogs.java.net/blog/joshy/archive/2005/11/netbeans_on_mac.html>
Even if nothing changes, at least you'll have eliminated a possible
culprit, which may be useful.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
