Memory leak: Juno, SBT, Play, or ScalaIDE?

[virtualeyes]

I am giving eclipse 1GB RAM to work with.

Running Play 2.1 Scala with ~run, after some time results in my 8GB
RAM machine swapping into disk, which should never happen if
applications stay within their allocated bounds.

Not sure where the issue is, but I do see that closing Scala IDE/Juno
did free up 3 GB RAM.

Might be a Play issue as well, SBT will throw permgen errors after
some time in ~run mode.

Just wondering if anyone else is experiencing this...

[Nils Kilden-Pedersen]

Probably something close to what's described here:

http://frankkieviet.blogspot.com/2006/10/classloader-leaks-dreaded-permgen-space.html

[Renato Garcia]

Regarding Juno, there is a known performance problem with this release,
not related to the Scala IDE though.
There are a couple of refs on this on the Google, and here is the issue
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272. This might be
contributing to what you are experiencing.

[Eric Molitor]

A few more points. You might need to add more perm gen space for projects with very large classpaths. If you believe you are running into some of the known issues with Juno and are feeling adventurous try the Kepler milestone builds. If you just want to put your head down and code with the least fiddling and worry use Indigo. :)

- Eric

[virtualeyes]

Yes, there are sbt-play permgen leaks in development; the only time I
get an OOME is via sbt play ~run

That may impact Juno as well since sbt runs the build show while Juno
follows.

On Nov 9, 8:42 pm, Nils Kilden-Pedersen <nil...@gmail.com> wrote:
> Probably something close to what's described here:
>

> http://frankkieviet.blogspot.com/2006/10/classloader-leaks-dreaded-pe...

[virtualeyes]

I had already read through this in regard to switching between scala/
java and xml/html/js static file slooooooow-ness.

Wound up stripping out Aptana plugin from Juno and installing it
standalone -- that was a major developer experience enhancement ;-)

On Nov 10, 8:34 am, Renato Garcia <renatao.gar...@gmail.com> wrote:
> Regarding Juno, there is a known performance problem with this release,
> not related to the Scala IDE though.

> There are a couple of refs on this on the Google, and here is the issuehttps://bugs.eclipse.org/bugs/show_bug.cgi?id=385272. This might be

[virtualeyes]

Thanks, I am normally feeling adventurous, tend to go with the
bleeding edge, but in this case, yes, may go back to Indigo just to
see how performance/stability differs (can't remember, have been on
Juno over 6 months...)

I will say that Scala IDE itself is working quite nicely, semantic
highlighting is so very nice on the eye sockets....

[Eric Molitor]

Let us know how you get along. 

- Eric