Community
Participate
Working Groups
Whenever I try to perform a rename refactoring the eclipse IDE crashes. The refactoring starts as usual, but just when it's about to end (before saving the refactored classes), the IDE dissappears. This is what's in the log file: !SESSION 2006-05-15 20:09:59.215 ----------------------------------------------- eclipse.buildId=I20060428-1315 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/gpremer/src/eclipse3.2-wkspc !ENTRY org.eclipse.core.expressions 4 4 2006-05-15 21:10:21.714 !MESSAGE Unknown expression element objectClass !ENTRY system.bundle 4 0 2006-05-15 21:23:55.835 !MESSAGE FrameworkEvent.ERROR !SESSION Mon May 15 21:23:58 CEST 2006 ----------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 !SESSION 2006-05-16 20:30:32.963 ----------------------------------------------- eclipse.buildId=I20060428-1315 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/gpremer/src/eclipse3.2-wkspc !ENTRY org.eclipse.core.resources 2 10035 2006-05-16 20:30:45.440 !MESSAGE A workspace crash was detected. The previous session did not exit normally. !ENTRY org.eclipse.core.expressions 4 4 2006-05-16 20:32:03.851 !MESSAGE Unknown expression element objectClass
Could you please provide a VM dump? What VM are you using? Are you on 64bits or 32bits platform ? Also could you please try with 3.2RC4? You are using 3.2RC2. Thanks.
I'm on an AMD 64 Platform (JDK + Eclipse). Will try RC4 when I'm home from work. Saw this problem occurring in earlier milestones too.
(In reply to comment #1) > Could you please provide a VM dump? Can you advise how to provide a VM dump? There's nothing beyond what I already sent in the logs. I appears eclipse takes the whole VM down in a very hard way, so eclipse is possibly just triggering a bug in the JDK. Will try on a JDK1.6beta as well.
Open a console with -consolelog on the Eclipse command line. You might also want to check bug 71987. This is likely a dup.
The VM dump should be located in your current user directory.
Moving to UI
(In reply to comment #6) > Moving to UI > (In reply to comment #4) > Open a console with -consolelog on the Eclipse command line. > You might also want to check bug 71987. > This is likely a dup. > Checked bug 71897, but that one should be fixed in 1.5.0_06, which I'm using. Anyway, checked with jdk1.6beta/3.2RC2 and jdk1.5.0_06/3.2RC4 and can't reproduce the bug. So far so good. Then tried jdk1.5.0/3.2RC2 but can't reproduce either! Bug 71987 suggests that the state of the workspace may have an influence. Did multiple "--clean"s to use the other JVM/Eclipse combinations, so this may have had an effect. Will keep on using jdk1.5.0/3.2RC2 for a while to try and trigger a crash condition & will keep you posted.
setting to 'remind' until you have more information or we find a similar problem.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
