Eclipse "not enough space" error

minnsey wrote on Tue Nov  6 10:57:23 CET 2007:

Hi,

Apologies if this has been covered before, I have looked but been unable
to find anything.

I'm occasionally getting errors like this when trying to debug perl scripts.

Failed to execute command line: "perl" "/home/me/Documents/Projects/ABC.metadata/.plugins/org.epic.debug/get_env.pl"
"1194342470148 "
Not enough space

I also occasionally get "Not enough space" errors when opening up a perl
workspace, which has editors left open.

I'm guessing its a memory issue but i don't know. Can anyone give me any
pointers.

FYI: I'm running eclipse 3.3 on solaris x86, with the following settings:

/opt/eclipse-gtk-3.3RC4/eclipse  -clean -vmargs -Dawt.toolkit=sun.awt.X11.XToolkit
-Xms512M -Xmx1024M

Thanks,

Mike

jploski wrote on Tue Nov  6 19:49:15 CET 2007:

This might be also referring to disk space (wild guess). In any case, you
should inspect the error log in $WORKSPACE/.metadata/.log and post the full
exception stack trace of it.

minnsey wrote on Fri Nov  9 09:45:13 CET 2007:

Hi

Sorry should have posted the stack trace before, here it is. I don't think
its disk space, at least not overall disk space as the disk file systems
are only a max of 25% full.

Cheers

Mike

!ENTRY org.epic.perleditor 4 0 2007-11-08 17:15:57.976
!MESSAGE Failed to execute command line: "perl" "/home/m.minns/Documents/Projects/DigitalMarketeer/.metadata/.plugins/org.epic.debug/get_env.pl"
"1194542155800 "
!STACK 0
java.io.IOException: Not enough space
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.(UNIXProcess.java:53)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
        at java.lang.Runtime.exec(Runtime.java:591)
        at org.epic.core.util.ProcessExecutor.execute(ProcessExecutor.java:103)
        at org.epic.core.util.ProcessExecutor.execute(ProcessExecutor.java:71)
        at org.epic.core.util.PerlExecutor.execute(PerlExecutor.java:84)
        at org.epic.debug.PerlDebugPlugin.runHelperScript(PerlDebugPlugin.java:548)
        at org.epic.debug.PerlDebugPlugin.readNativeEnv(PerlDebugPlugin.java:507)
        at org.epic.debug.PerlDebugPlugin.getDebugEnv(PerlDebugPlugin.java:171)
        at org.epic.debug.local.LocalLaunchConfigurationDelegate.startPerlProcess(LocalLaunchConfigurationDelegate.java:287)
        at org.epic.debug.local.LocalLaunchConfigurationDelegate.startRunTarget(LocalLaunchConfigurationDelegate.java:311)
        at org.epic.debug.local.LocalLaunchConfigurationDelegate.doLaunch(LocalLaunchConfigurationDelegate.java:36)
        at org.epic.debug.LaunchConfigurationDelegate.launch(LaunchConfigurationDelegate.java:28)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:766)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:899)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1102)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

minnsey wrote on Fri Nov  9 09:57:35 CET 2007:

Hmm googling a bit e.g.:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4965592

It looks like it could be a lack of memory, tmp or swap space, outside of
the jvm memory, available to spawn a new unix process, i.e. perl.