Skip to main content



      Home
Home » Newcomers » Newcomers » Eclipse running problem
Eclipse running problem [message #217565] Sat, 23 June 2007 18:21 Go to next message
Eclipse UserFriend
Originally posted by: jack.w.rae.googlemail.com

At first I was having problems with java heap memory when loading eclipse
- however now I load it with the command: ./eclipse -clean -vmargs
-XX:MaxPermSize=128M in the eclipse directory.

Now it starts to run, but then I get an error message, I am running Suse
10.2 and Konsole displays this:
Quote:
An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb7de96fb, pid=10175, tid=3084684160
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_08-b03 mixed mode)
# Problematic frame:
# C [libc.so.6+0x206fb]


and in the error report file it says this:
Quote:
!SESSION 2007-06-23 23:15:38.166
-----------------------------------------------
eclipse.buildId=M20060921-0945
java.version=1.5.0_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_GB
Command-line arguments: -os linux -ws gtk -arch x86 -clean

!ENTRY org.eclipse.update.configurator 2007-06-23 23:15:43.546
!MESSAGE Could not install bundle
plugins/org.eclipse.platform.doc.isv_3.2.1.r321_v2006030.jar null


What do I need to do to finally get eclipse on it's feet?
Re: Eclipse running problem [message #217865 is a reply to message #217565] Mon, 25 June 2007 11:08 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: wegener.cboenospam.com

Heap memory is manipulated using the -Xms and -Xmx arguments. The argument
you entered is for the perm gen area. This is something completely
different.
"jack" <jack.w.rae@googlemail.com> wrote in message
news:52f30ee817be321a255c363984d2ea0b$1@www.eclipse.org...
> At first I was having problems with java heap memory when loading eclipse
> - however now I load it with the command: ./eclipse -clean -vmargs
> -XX:MaxPermSize=128M in the eclipse directory.
>
> Now it starts to run, but then I get an error message, I am running Suse
> 10.2 and Konsole displays this:
>
Quote:
An unexpected error has been detected by HotSpot Virtual Machine:
> #
> # SIGSEGV (0xb) at pc=0xb7de96fb, pid=10175, tid=3084684160
> #
> # Java VM: Java HotSpot(TM) Client VM (1.5.0_08-b03 mixed mode)
> # Problematic frame:
> # C [libc.so.6+0x206fb]

>
> and in the error report file it says this:
>
Quote:
!SESSION 2007-06-23 23:15:38.166
> -----------------------------------------------
> eclipse.buildId=M20060921-0945
> java.version=1.5.0_08
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_GB
> Command-line arguments: -os linux -ws gtk -arch x86 -clean
>
> !ENTRY org.eclipse.update.configurator 2007-06-23 23:15:43.546
> !MESSAGE Could not install bundle
> plugins/org.eclipse.platform.doc.isv_3.2.1.r321_v2006030.jar null
>

> What do I need to do to finally get eclipse on it's feet?
>
>
>
Re: Eclipse running problem [message #217882 is a reply to message #217865] Mon, 25 June 2007 11:51 Go to previous message
Eclipse UserFriend
Originally posted by: jack.w.rae.googlemail.com

Thank you for your advice. With the argument (in super-user mode)
/eclipse -clean -Xms[whatever] -Xmx[whatever] I always get an error
message:

Could not reserve enough space for object heap
Could not create the Java virtual machine.

if I use the opening command: ./eclipse -clean -vmargs -Xms[whatever]
-Xmx[whatever] then I get the same error as before (eclipse begins to run
first)

I have 512mb of ram (which, yes, does need to be upgraded) and I am
normally setting minimum values of 64M or 128M and maximum values of all
sorts from 512M to 128M. I always seem to get the complaint of not having
enough space for object heap however.
Previous Topic:Alternative Configurations
Next Topic:Lock editor
Goto Forum:
  


Current Time: Fri Apr 25 21:35:45 EDT 2025

Powered by FUDForum. Page generated in 0.08460 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top