The bugtrack is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304149


.

I installed the 64-bit version of Eclipse 3.5.2 by untarring it into my home directory, installed the Aptana Studio plugin via the method in your bug report, and didn't get the crash. I was able to restart Eclipse a few times and also play with the Aptana web perspective.

Hi Dugan,

The bug is for the 32 bit version of Slackware 13.0 and Eclipse, the latter being installed as a SlackBuild package. We reproduced this bug on four (not identical) machines.

The de facto recommended convention (dare I say standard ), is to install using the Slackware package management system, with packages created via the SlackBuild whenever possible, although I'm also a fan of compiling and installing by hand (As well as rolling my own Packages irrespective of SlackBuilds) as well

Each machine had various plugins installed other than Aptana, including Epic-IDE, on three of them. I also posted in the Aptana forums and found a myriad of similar issues in their archived forums, yet to date have not had anyone address the issue there (Those similar issues by many others weren't addressed in the earlier forum system they were using either).

Aptana is a nice development environment, so I just may try a shotgun install using your Eclipse installation method on a machine (in a 32 bit environs) and give that a try.

We're looking forward to RadRails3, but are prepared to continue using NetBeans as well.

Thanks for the input!

I'm having this same problem and I don't hava Aptana installed. Can't seem to find the reason why is happening but is the same log output as the bug tracker indicates.