Community
Participate
Working Groups
Build Identifier: Cannot open the Eclipse . A dialog shows an error ... see .log Then doing what clear ${workspace}\.metadata\.log and delete elipse-jee-indigo-win32-x86_64\configuration\org.eclipse.update can solve the problem . Reproducible: Always Steps to Reproduce: Set -XX:+UseLargePages in eclipse.ini, then Eclipse always crashes if WindowOS close and eclipse is still working. 1. Set -XX:+UseLargePages in eclipse.ini 2. the loccal security to open the largePage Win7 OS , guides from http://www.oracle.com/technetwork/java/javase/tech/largememory-jsp-137182.html 3. Reboot OS. 4. Open eclipse-jee 5. Donot close the Running Eclipse Close OS. 6. Open eclipse , errros occur... Last , 4-6 always happend.
Please attach the log files in question. What JRE are you using to run Eclipse?
Created attachment 201144 [details] eclipse error.
Created attachment 201145 [details] eclipse log .log about 21:51 I close os , close Eclipse by OS. about 21:53 I starts it
(In reply to comment #1) > Please attach the log files in question. > > What JRE are you using to run Eclipse? JRE from : jdk-6u26-windows-x64.exe OS : win7 x64 Eclipse: Eclipse Java EE IDE for Web Developers. Version: Indigo Release Build id: 20110615-0604 From Eclipse Installation Details -> Configuration: -vm C:\Program Files\Java\jdk\bin\..\jre\bin\server\jvm.dll eclipse.home.location=file:/D:/Program Files/eclipse-jee-indigo-win32-x86_64/ eclipse.launcher=D:\Program Files\eclipse-jee-indigo-win32-x86_64\eclipse.exe eclipse.launcher.name=Eclipse eclipse.p2.data.area=@config.dir/../p2/ eclipse.p2.profile=epp.package.jee eclipse.product=org.eclipse.epp.package.jee.product eclipse.startTime=1312898277679 eclipse.vm=C:\Program Files\Java\jdk\bin\..\jre\bin\server\jvm.dll eclipse.vmargs=-Dosgi.requiredJavaVersion=1.5 -Xms256m -Xmx512m -XX:-UseLargePages -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:+OptimizeStringConcat -Duser.name=LinZuXiong -XX:MaxPermSize=256m -Djava.class.path=D:\Program Files\eclipse-jee-indigo-win32-x86_64\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar equinox.use.ds=true file.encoding=GBK file.encoding.pkg=sun.io
The error with SWT handles typically occurs when there are too many resources open in the OS. Not quite clear to me what can be done here at the moment.
(In reply to comment #5) > The error with SWT handles typically occurs when there are too many resources > open in the OS. Not quite clear to me what can be done here at the moment. Is it a bug ,or not?
I must admit I do not understand the bug report. What do you mean by the OS close? Do you hibernate it? Or just put in a sleep mode? Then you wake it up, and then Eclipse crashes? Or maybe do you close OS with Eclipse running, shutdown your PC, and then your are not able to start your Eclipse anymore? Could you clarify the reproduction steps as well as what you do to recover from the crash?
(In reply to comment #7) > I must admit I do not understand the bug report. What do you mean by the OS > close? Do you hibernate it? Or just put in a sleep mode? Then you wake it up, > and then Eclipse crashes? Or maybe do you close OS with Eclipse running, > shutdown your PC, and then your are not able to start your Eclipse anymore? > > Could you clarify the reproduction steps as well as what you do to recover from > the crash? I mean that 1.I power off the os or I just restart the os with Eclipse running. 2.Enter the os 3.double click the eclipse.exe~~~ crash happens. I am not able to start your Eclipse anymore -- It is clear?
Do you get this problem if you kill Eclipse manually instead of having Windows kill it when it shuts down?
(In reply to comment #9) > Do you get this problem if you kill Eclipse manually instead of having Windows > kill it when it shuts down? If I kill Eclipse manually ,this problem that low frequence will happend sometimes .
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
