Question

I’d like to hear, if anyone else encounters the same problems, and doesn’t use Google’s GWT (2.0) plugins:

Sometimes, my Eclipse 3.5 (Cocoa) slows down after some time of usage (>=30 minutes), so that things like maximizing an editor or moving the splitters becomes unbearably slow (reacting only after several seconds). After an Eclipse restart, everything’s fine again.

I’m not running low on memory (neither free RAM, nor memory available to Eclipse – Heap/Stack/PermGenSpace), and my system specs are not too bad.

I know exactly one other person so far, who sees the same problem – but he also uses the GWT plugins. Since these issues appear irregularly, they’re hard to track. Before creating an issue on the GWT bug tracker, I’d like to find out, if this also happens for somebody without Google’s plugins.

Thanks,

Chris

Edit:

I’m running Snow Leopard 10.6.2, Eclipse 3.5 Cocoa 32-bit.

eclipse.ini:

-startup
../../../plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.0.1.R35x_v20090707
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:MaxPermSize=280m
-Xdock:icon=../Resources/Eclipse.icns
-Xms54m
-Xmx560m

Answer 1

A good eclipse.ini can help.
But as mentioned in “Horrible eclipse performance on macbook pro running 10.5.8” (which kind of illustrate the fact that performance issue can happen with Galileo without GWT), it can depend on the OS version (Snow Leopard or Leopard).