Community
Participate
Working Groups
Created attachment 105309 [details] Word .doc showing the JVM terminated screen Build ID: 20080618-1010_eclipse-jee-ganymede-RC5-win32.win32.x86 Steps To Reproduce: 1. Install 20080618-1010_eclipse-jee-ganymede-RC5-win32.win32.x86 2. Copy the icon to the desktop 3. Double click the icon to start it. You get an error screen More information: I can upload a screen shot of the screen with the JVM terminated message / dump.
We need more information. Is there anything in your log files? Check in your configuration and workspace/.metadata directories.
There are no log files in the configuration/ directory (no .metadata either). It crashes before getting the point where I select a workspace so there's no workspace/.metadata to check either. Is there anywhere else I can look?
Are you on a 32-bit or 64-bit XP? You can try running it from the command line. eclipse.exe -consoleLog -debug And also check for hs_err_pid log files.
I'm on a 32 bit Windows XP system (SP 2). Running from the command line with eclipse.exe -consoleLog -debug gives the same result, but I also get a dialog box saying No Exit Data Availalbe. Other test builds have worked for me with no problems. Try running this buile it on WinXP and see if you get the same result.
I don't know where you got rc5, but I downloaded eclipse-jee-ganymede-RC4-win32.zip and it runs fine on Vista (I don't have XP).
I got it right here: http://www.eclipse.org/epp/download.php Your comment is frankly pretty stupid. They've obviously broken something in this build of RC5 and saying that RC4 works on Vista is irrelevant. Please do something constructive and let the developers know that they've really broken their last build.
(In reply to comment #6) > I got it right here: > > http://www.eclipse.org/epp/download.php Thanks for the link, that would explain why I couldn't find it. I was looking at this page myself. http://www.eclipse.org/downloads/packages/ > Your comment is frankly pretty stupid. They've obviously broken something in > this build of RC5 and saying that RC4 works on Vista is irrelevant. Since I didn't know where to find an RC5 build, I thought I'd try an RC4 build in case a) it was broken in RC4 and/or b) it doesn't work on Vista also (this would help the developers identify whether it's an XP-only issue or a larger Windows-related problem). Anyway, I just downloaded and unzipped that 20080618_1010 jee build and both double-clicking and creating a shortcut to put on your desktop (per your comment 0) seems to start fine on Vista here.
The crash is caused by this argument in eclipse.ini: -Xmx1024m When I set it to -Xmx768m it works. I can solve and reproduce this problem by switching back and forth between 768m and 1024m. There should be no problem with this setting as Alex Blewitt mentions it here: http://www.eclipsezone.com/articles/eclipse-vms/
The problem is this setting in eclipse.ini: -Xmx1024m When I set it back to 768m it works. I can reproduce and solve the problem by switching back and forth between 1024m / 768m.
(In reply to comment #6) > I got it right here: > > http://www.eclipse.org/epp/download.php > > Your comment is frankly pretty stupid. They've obviously broken something in > this build of RC5 and saying that RC4 works on Vista is irrelevant. > > Please do something constructive and let the developers know that they've > really broken their last build. > For the record, Remy is the most constructive contributor we have. He's not a committer on our project and he doesn't get paid to do this - he's trying to help you because he wants to. Calling his comments stupid and exposing yourself to be insufferably rude is probably not going to get the results you expect. I've downloaded the build in question and have tried to reproduce this on XP. It works fine for me on a 1.5.0_111-b03 Sun VM. I'm going to send this off to the EPP team. If other builds of theirs work as you say perhaps they can shed some light on this. Andrew, has anything changed in the launcher that might explain this?
Trying to reproduce this... but everything works fine here: * Using a Windows XP SP2 virtual machine with 512MB memory (!) * Tested with jre1.5.0_15 and jre1.6.0_04 * This EPP build still uses Eclipse Platform I20080613-2000 as basis * Setting eclipse.ini: -Xmx1024m (before the first start) * Started Eclipse from cmd.exe: eclipse -consoleLog -vm C:\Programme\Java\jre1.5.0_15\bin\java * Eclipse starts with 2 known exceptions in the log * Look at the details below One further comment: This is not a well-tested version, it is 'just a nightly build' (but of course, it should work). %< -------------------------------------------------------------- eclipse.buildId=I20080613-2000 eclipse.commands=-os win32 -ws win32 -arch x86 -showsplash -launcher C:\test\eclipse\eclipse.exe -name Eclipse --launcher.library C:\test\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800\eclipse_1114.dll -startup C:\test\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar -exitdata 720_7c4 -consoleLog -vm C:\Programme\Java\jre1.5.0_15\bin\java.exe eclipse.consoleLog=true eclipse.ee.install.verify=false eclipse.home.location=file:/C:/test/eclipse/ eclipse.launcher=C:\test\eclipse\eclipse.exe eclipse.p2.data.area=@config.dir/../p2 eclipse.p2.profile=PlatformProfile eclipse.product=org.eclipse.platform.ide eclipse.startTime=1213884804472 eclipse.vm=C:\Programme\Java\jre1.5.0_15\bin\java.exe eclipse.vmargs=-Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx1024m -XX:MaxPermSize=256M -jar C:\test\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar file.encoding=Cp1252 file.encoding.pkg=sun.io file.separator=\ java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment java.awt.printerjob=sun.awt.windows.WPrinterJob java.class.path=C:\test\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar java.class.version=49.0 java.endorsed.dirs=C:\Programme\Java\jre1.5.0_15\lib\endorsed java.ext.dirs=C:\Programme\Java\jre1.5.0_15\lib\ext java.home=C:\Programme\Java\jre1.5.0_15 java.io.tmpdir=C:\DOKUME~1\mknauer\LOKALE~1\Temp\ java.library.path=C:\Programme\Java\jre1.5.0_15\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version=1.5.0_15-b04 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.5 java.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.5.0_15 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) Client VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=1.5.0_15-b04 %< --------------------------------------------------------------
Hmm, one idea, maybe you can comment on it, Dean: The eclipse.ini file is generated on a Unix system, therefore it doesn't contain carriage return - line feeds and may look broken on Windows (everything in one line, depending on the editor that you are using). How did you edit the file? Which editor did you use? Or how does it look like after your changes? Every parameter on its own line, like this example here? -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256M -framework plugins\org.eclipse.osgi_3.4.0.v20080605-1900.jar -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx1024m
There are numerous articles and forum discussions about the jvm failing to start with "big" heap sizes. Basically because the jvm (or the OS?) needs the heap size to be one continues junk and not fragmented. Therefore it depends on ones concrete OS installation and especially which dll's are already in memory when trying to allocate a big piece of continues memory. You could try to run eclipse from a windows console to see the jvm's output (maybe you have to specify java.exe explicitly so that eclipse does not use javaw.exe) Search the internet for "could not reserve enough space for object heap" (this is the output generated if the jvm fails to allocate the memory) for more articles describing this "problem".
So this is a JVM failure because it can't allocate 1024m ? Interesting since I have 2 GB on this machine and the amount of memory being used prior to starting ganymede is 499MB. Since this varies from machine to machine (Markus was able to run with 1024m on a virtual machine with only 512 MB RAm) the "fix" is probably to give a meaningful error message in the popup dialog instead of just a dump of vmargs. The Help doucments that mention -Xmx should probably also mention that this can be an issue. I'm in favor of resolving this by making a documentation change and adding a meaningful message to the popup dialog. My eclipse.ini is below. I edited this with TextPad, and it picks up the line breaks properly. -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256M -framework plugins\org.eclipse.osgi_3.4.0.v20080605-1900.jar -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx768m
The amount of free space is unfortunately no guarantee that this space is not fragmented. However I'm wondering: your xms setting defines only 40mb of initial heap, thus the jvm starts to request 40mb from the OS and grows this as the need arises. If changing your xmx setting from 1024 to 768m makes the difference this would mean that your installation tries to allocate really more than 768m in the case where you defined 1024m. Maybe you should really try to run eclipse with from a console with something like "eclipse -vm c:\jdk\bin\java.exe" and check the output.
Comment #13 is correct, see bug 188968. -Xmx1024m is likely too high (especially as a default). On windows, when using the JNI invocation API to load the vm in the eclipse process, windows dlls can be loaded in the middle of the address space, fragmenting it and not leaving any one block of memory large enough for the vm. Running with -vm pointing to a java.exe (as done in comment #11) avoids this issue as java is started in a separate process from the eclipse launcher and the windows dlls are not loaded until after java has started.
I added the following to eclipse.ini (before the -vmargs) and everything is fine: -vm c:\bin\jdk1.5.0_12\bin\javaw.exe This should be documented (especially comment 16).
Decreasing severity because there is a workaround available.
Created attachment 105931 [details] Eclipse 3.4 crash on startup I am using CentOS 5.2 x64. I can't start Eclipse 3.4 (stable release from yesterday). I have tried modeling and j33 package.
I also have tried starting 3.4 on Centos 5.2 x86-64with a crash. It seems related to Firefox/Mozilla libraries. Centos 5.1 x86-64 doesn't have any issues. I've tried both Sun JVM 1.6u6 and 1.5u10 64-bit. Both would result in crashes.
(In reply to comment #20) > I also have tried starting 3.4 on Centos 5.2 x86-64with a crash. It seems > related to Firefox/Mozilla libraries. If it's Mozilla related, you should check out bug 213194 or bug 236724.
Hello! I have the same problem after installing eclipse-jee-ganymede-win32.zip on windows xp 64 bit version 2003 SP1. JRE 1.6.07 for xp 64 bit. Is there a package for 64 bit windows that will work? Or is it some other cause of this error? No exit data available. Config (in debug console): -Djava.class.path=F:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080 509-1800.jar -os win32 -ws win32 -arch x86 -showsplash F:\eclipse\\plugins\org.eclipse.platform_3.3.100.v200806172000\splas h.bmp -launcher F:\eclipse\eclipse.exe -name Eclipse --launcher.library F:\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x 86_1.0.100.v20080509-1800\eclipse_1114.dll -startup F:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080509-1800. jar -framework plugins\org.eclipse.osgi_3.4.0.v20080605-1900.jar -consoleLog -debug -vm C:\Program Files\Java\jre1.6.0_07\bin\server\jvm.dll -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx768m -XX:MaxPermSize=512M -Djava.class.path=F:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v20080 509-1800.jar
(In reply to comment #22) > Is there a package for 64 bit windows that will work? > Or is it some other cause of this error? For a workaround, you can try what's been suggested in comment 17. In your case, I think it would be something like C:\Program Files\Java\jre1.6.0_07\bin\java.exe.
I've downloaded eclipse-SDK-3.4-win32-x86_64.zip and it works now.
(In reply to ) As per comment #16, it looks like this could be closed as a duplicate of bug 188968 from an implementation point of view. From a User's point of view, it seems like more users could run into this before it gets actually fixed, so the problem and the workaround (as per comment #17) should be documented in the Platform and/or JEE release notes. Could somebody who knows where these are check if it has been documented for Ganymede SR1?
I will mark as a dup. I'm not sure where to document it, but I actually haven't seen this problem reported very often ... at least not enough to merit a release not. (And, if there are enough to merit a release note, perhaps Platform could add it in a FAQ?) *** This bug has been marked as a duplicate of bug 188968 ***
