Comment 1 Gurjeet 2010-06-25 20:16:01 EDT

Created attachment 172827 [details]
log file

Comment 2 Darin Wright 2010-06-28 09:38:27 EDT

Looks like your using 3.4.2. Have you been able to see if the problem occurrs on a newer version of Eclipse. You're -Xmx and -Xms arguments look reasonably large, so I'm not sure what's causing the OOME. Moving to JCore for comment as the issue appears to happening when running JDT code.

Comment 3 Olivier Thomann 2010-06-28 10:58:27 EDT

We would need more information about this failure.
The .log doesn't give any clue why it failed.
Are you using APT?

Did you try moving to a newer build ?

Comment 4 Gurjeet 2010-06-28 12:27:24 EDT

Created attachment 172922 [details]
Not able to create java virtual Machine.

Comment 5 Gurjeet 2010-06-28 12:32:23 EDT

(In reply to comment #3)
> We would need more information about this failure.
> The .log doesn't give any clue why it failed.
> Are you using APT?
> Did you try moving to a newer build ?

Itried using the newer version of eclipse helios. 
Version = 3.6.0
Build Id :  I20100608-0911
I got the following error :
Error occurred during initialization of VM
Could not reserve enough space for object heap
I am also attaching the screen shot of the same.
The contents of the Eclipse.ini file :
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
org.eclipse.platform
-launcher.XXMaxPermSize
256m
-launcher.defaultAction
-vmargs
-Xms512m
-Xmx656m

I am not able to assign more than 656m memory.If I assign more than that it says not able to create java virtual machine.

Comment 6 Gurjeet 2010-06-28 12:33:12 EDT

(In reply to comment #5)
> (In reply to comment #3)
> > We would need more information about this failure.
> > The .log doesn't give any clue why it failed.
> > Are you using APT?
> > Did you try moving to a newer build ?
> Itried using the newer version of eclipse helios. 
> Version = 3.6.0
> Build Id :  I20100608-0911
> I got the following error :
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> I am also attaching the screen shot of the same.
> The contents of the Eclipse.ini file :
> -startup
> plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
> -launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
> org.eclipse.platform
> -launcher.XXMaxPermSize
> 256m
> -launcher.defaultAction
> -vmargs
> -Xms512m
> -Xmx656m
> I am not able to assign more than 656m memory.If I assign more than that it
> says not able to create java virtual machine.

I am not using APT.

Comment 7 Olivier Thomann 2010-06-28 12:36:19 EDT

Please use a 1.5 VM at least.

Comment 8 Gurjeet 2010-06-28 12:43:42 EDT

(In reply to comment #7)
> Please use a 1.5 VM at least.

I am using 1.6. Here is the error I got when I started with eclipse galileo
eclipse.buildId=M20090917-0800
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -Xmx1024m
Command-line arguments:  -os win32 -ws win32 -arch x86 -Xmx1024m

!ENTRY org.eclipse.core.jobs 4 2 2010-06-28 09:35:27.546
!MESSAGE An internal error occurred during: "Building workspace".
!STACK 0
java.lang.OutOfMemoryError: Java heap space
	at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsCharArray(Util.java:398)
	at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1168)
	at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1137)
	at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:79)
	at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:166)
	at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.core.jobs 4 2 2010-06-28 09:36:53.242
!MESSAGE An internal error occurred during: "Building workspace".
!STACK 0
java.lang.OutOfMemoryError: Java heap space
	at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsCharArray(Util.java:398)
	at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1168)
	at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1137)
	at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:79)
	at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:166)
	at java.lang.Thread.run(Unknown Source)

Comment 9 Gurjeet 2010-06-28 12:57:34 EDT

Message :Cannot connect to VM

Session Data:
eclipse.buildId=I20100608-0911
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503 org.eclipse.platform -launcher.XXMaxPermSize 256m -launcher.defaultAction
Command-line arguments:  -os win32 -ws win32 -arch x86 -launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503 org.eclipse.platform -launcher.XXMaxPermSize 256m -launcher.defaultAction

Exception Stack Trace:
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at org.eclipse.jdi.internal.connect.SocketTransportService.accept(SocketTransportService.java:95)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:56)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:135)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:107)
at java.lang.Thread.run(Unknown Source)

Comment 10 Olivier Thomann 2010-06-28 13:10:04 EDT

How big is your workspace ?
Right now we cannot do anything with what we have. I have a pretty big workspace and it can start without a problem.

Darin, would you have any idea about the connection issue (comment 9)?

Comment 11 Gurjeet 2010-06-28 13:14:33 EDT

(In reply to comment #10)
> How big is your workspace ?
> Right now we cannot do anything with what we have. I have a pretty big
> workspace and it can start without a problem.
> Darin, would you have any idea about the connection issue (comment 9)?

My Workspace is 1.15 GB.

Comment 12 Olivier Thomann 2010-06-28 13:26:51 EDT

Please provide your eclipse.ini.

Comment 13 Gurjeet 2010-06-28 13:29:40 EDT

(In reply to comment #12)
> Please provide your eclipse.ini.

-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
org.eclipse.platform
-launcher.XXMaxPermSize
256m
-launcher.defaultAction
-vmargs
-Xms512m
-Xmx656m

Comment 14 Darin Wright 2010-06-28 13:33:44 EDT

(In reply to comment #10)
> Darin, would you have any idea about the connection issue (comment 9)?

The connector attempts to attach to a socket. It can timeout if it's waiting
too long. The timeout value is specified via the "Preferences > Java > Debug >
Launch timeout" value, and defaults to 20 seconds. It's possible that a
firewall could also disallow a connection.

Comment 15 Olivier Thomann 2010-06-28 13:43:54 EDT

(In reply to comment #13)
> -startup
> plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
> -launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
> org.eclipse.platform
> -launcher.XXMaxPermSize
> 256m
> -launcher.defaultAction
> -vmargs
> -Xms512m
> -Xmx656m
I have "--" in front of launcher options instead of "-".

Comment 16 Stephan Herrmann 2010-06-28 14:01:27 EDT

(In reply to comment #15)
> (In reply to comment #13)
> > -startup
> > plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
> > -launcher.library
> > plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
> > org.eclipse.platform
> > -launcher.XXMaxPermSize
> > 256m
> > -launcher.defaultAction
> > -vmargs
> > -Xms512m
> > -Xmx656m
> I have "--" in front of launcher options instead of "-".

Plus, the line "org.eclipse.platform" should probably have a preceding line
"-showsplash". Has this file been edited manually or is it the result
of some p2 update operation?

Comment 17 Gurjeet 2010-06-28 14:24:22 EDT

(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #13)
> > > -startup
> > > plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
> > > -launcher.library
> > > plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
> > > org.eclipse.platform
> > > -launcher.XXMaxPermSize
> > > 256m
> > > -launcher.defaultAction
> > > -vmargs
> > > -Xms512m
> > > -Xmx656m
> > I have "--" in front of launcher options instead of "-".
> Plus, the line "org.eclipse.platform" should probably have a preceding line
> "-showsplash". Has this file been edited manually or is it the result
> of some p2 update operation?

I manually edited the file as I was trying to resolve the issue by my self.

Comment 18 Olivier Thomann 2010-06-28 14:29:06 EDT

This is mine:
-console
-vm
D:/jdks/jdk6_20/jre/bin/java.exe
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-XX:MaxPermSize=300M
-Xss1M
-Xms80m
-Xmx800M

Please try it and update the vm argument path.
Let me know if this works.

Comment 19 Gurjeet 2010-06-28 14:35:02 EDT

(In reply to comment #18)
> This is mine:
> -console
> -vm
> D:/jdks/jdk6_20/jre/bin/java.exe
> --launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
> -startup
> plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -XX:MaxPermSize=300M
> -Xss1M
> -Xms80m
> -Xmx800M
> Please try it and update the vm argument path.
> Let me know if this works.

Now I got this error.
See the attached screen shot.EclipseIniError

Comment 20 Gurjeet 2010-06-28 14:35:44 EDT

Created attachment 172936 [details]
Eclipse Ini Error

Comment 21 Olivier Thomann 2010-06-28 14:39:11 EDT

What is the line where you declare the VM path?
You have a space in your VM path.

Comment 22 Gurjeet 2010-06-28 14:48:38 EDT

(In reply to comment #21)
> What is the line where you declare the VM path?
> You have a space in your VM path.

Here is my ini file.
-console
-vm
C:/jdks/jre6/bin/java.exe
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-XX:MaxPermSize=300M
-Xss1M
-Xms80m
-Xmx800M

Comment 23 Olivier Thomann 2010-06-28 14:53:38 EDT

This is not the path in your latest screenshot. Are you sure you are starting the right eclipse installation ?

Comment 24 Gurjeet 2010-06-28 14:58:26 EDT

(In reply to comment #23)
> This is not the path in your latest screenshot. Are you sure you are starting
> the right eclipse installation

I changed the settings so that there is no space in VM arguement.
Attached is the latest screen shot.

Comment 25 Gurjeet 2010-06-28 14:58:51 EDT

Created attachment 172941 [details]
Eclipse ini error 2

Comment 26 Olivier Thomann 2010-06-28 15:00:44 EDT

Andrew, any idea ?

Comment 27 Andrew Niefer 2010-06-28 16:01:14 EDT

(In reply to comment #0)
> It started happening two days ago. Whenever i launch my debugger it says 
> Error occurred during initialization of VM
> Could not reserve enough space for object heap

This message means the total of XXMaxPermSize + Xmx is too high and need to be lowered.  See bug 188968 for details.  This is likely the cause of the other socket connect problems as I believe the vm just exits after this.  The actual maximum values here depend on a lot of things and will vary from computer to computer.

> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments:  -Xmx1024m
> Command-line arguments:  -os win32 -ws win32 -arch x86 -Xmx1024m

Log entries that show the -Xmx args as part of the command-line/framework arguments indicate that the -Xmx1024m was not specified properly as a vm argument but was instead passed as a program arg.  This is likely the reason for the out of memory problems, since without the -Xmx the default is quite low.

The eclipse.ini in comment #13 has a bunch of problems in it, Olivier's eclipse.ini is better and will actually allow for higher XXMaxPermSize and -Xmx values because the vm is being forked in a separate process (since -vm to a java.exe was specified).  

"Java returned 1" means the java process started correctly, but failed early.  
There is no real indication of the cause of this.

I would suggest running "eclipsec" from the command prompt to see if any error messages get printed to the console.

Comment 28 Olivier Thomann 2010-06-29 14:18:13 EDT

Any update on this ?

Comment 29 Gurjeet 2010-06-29 14:25:04 EDT

(In reply to comment #28)
> Any update on this ?

There no error messages were printed on the console. My system has 3 GB of memory but still I am only able to allocate 800m for eclipse or in the run configuration. When I am building the system it is still showing me the Java heap space error.

Comment 30 Olivier Thomann 2010-06-30 11:29:19 EDT

Setting severity to normal.
Need more details on your workspace. Did you fix what Andrew suggested in comment 27?

Comment 31 Gurjeet 2010-06-30 17:24:44 EDT

(In reply to comment #30)
> Setting severity to normal.
> Need more details on your workspace. Did you fix what Andrew suggested in
> comment 27?

Yeah I did but I am getting the Java Heap Space error if I use the other ini file.

Comment 32 Olivier Thomann 2010-07-13 12:21:37 EDT

Your problem looks like a setup issue.
I don't know what we can do to help you. What happens if you use the default .ini file from Eclipse ?

Comment 33 Olivier Thomann 2010-07-21 21:32:04 EDT

Try adding:
-XX:MaxPermSize=512M

as part of the VM arguments.

Comment 34 Olivier Thomann 2010-09-02 13:12:29 EDT

Closing as WORKSFORME.
Given what I have, there is no much I can do.

Comment 35 Srikanth Sankaran 2010-09-14 00:19:22 EDT

Verified for 3.7 M2