Eclipse "not enough space" error

Mike Minns
  • Mike Minns

    Mike Minns - 2007-11-06


    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/" "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



    • Jan Ploski

      Jan Ploski - 2007-11-06

      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.

    • Mike Minns

      Mike Minns - 2007-11-09


      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.



      !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/" "1194542155800 "
      !STACK 0 Not enough space
              at java.lang.UNIXProcess.forkAndExec(Native Method)
              at java.lang.UNIXProcess.<init>(
              at java.lang.ProcessImpl.start(
              at java.lang.ProcessBuilder.start(
              at java.lang.Runtime.exec(
              at org.epic.core.util.ProcessExecutor.execute(
              at org.epic.core.util.ProcessExecutor.execute(
              at org.epic.core.util.PerlExecutor.execute(
              at org.epic.debug.PerlDebugPlugin.runHelperScript(
              at org.epic.debug.PerlDebugPlugin.readNativeEnv(
              at org.epic.debug.PerlDebugPlugin.getDebugEnv(
              at org.epic.debug.local.LocalLaunchConfigurationDelegate.startPerlProcess(
              at org.epic.debug.local.LocalLaunchConfigurationDelegate.startRunTarget(
              at org.epic.debug.local.LocalLaunchConfigurationDelegate.doLaunch(
              at org.epic.debug.LaunchConfigurationDelegate.launch(
              at org.eclipse.debug.internal.core.LaunchConfiguration.launch(
              at org.eclipse.debug.internal.core.LaunchConfiguration.launch(
              at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(
              at org.eclipse.debug.internal.ui.DebugUIPlugin$

      • Mike Minns

        Mike Minns - 2007-11-09

        Hmm googling a bit e.g.:

        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.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks