I'm having trouble running eclipse after download. I've played with the environment variables to add my most recent version of java, but the error still keeps occuring. Any suggestions are appreciated.
Stack: [0x02b50000,0x02b90000), sp=0x02b8fc38, free space=255k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0xc7b68] V [jvm.dll+0x6d69b] V [jvm.dll+0x6e901] V [jvm.dll+0x6e4e2] V [jvm.dll+0x71afb] V [jvm.dll+0xffd2b] V [jvm.dll+0x6d2fa] V [jvm.dll+0x6d98a] V [jvm.dll+0x11a6ae] V [jvm.dll+0x11a185] V [jvm.dll+0x11a325] V [jvm.dll+0x11a0ba] C [MSVCRT.dll+0x2a3b0] C [kernel32.dll+0xb50b]
VM_Operation (0x0006c66c): full generation collection, mode: safepoint, requested by thread 0x00355318
Other Threads: =>0x00a17df0 VMThread [id=1732] 0x00a1feb8 WatcherThread [id=1044]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event]) [0x003549b8/0x00000720] Threads_lock - owner thread: 0x00a17df0 [0x00354b38/0x000006e4] Heap_lock - owner thread: 0x00355318
Heap def new generation total 2880K, used 1422K [0x16a80000, 0x16da0000, 0x17e30000) eden space 2560K, 47% used [0x16a80000, 0x16bb3238, 0x16d00000) from space 320K, 60% used [0x16d00000, 0x16d30728, 0x16d50000) to space 320K, 0% used [0x16d50000, 0x16d50000, 0x16da0000) tenured generation total 37824K, used 7984K [0x17e30000, 0x1a320000, 0x26a80000) the space 37824K, 21% used [0x17e30000, 0x185fc1c0, 0x18633000, 0x1a320000) compacting perm gen total 16384K, used 16384K [0x26a80000, 0x27a80000, 0x2aa80000) the space 16384K, 100% used [0x26a80000, 0x27a80000, 0x27a80000, 0x27a80000) ro space 8192K, 62% used [0x2aa80000, 0x2af893f0, 0x2af89400, 0x2b280000) rw space 12288K, 46% used [0x2b280000, 0x2b80fe20, 0x2b810000, 0x2be80000)
The splash window comes up, a progress bar comes up and then the error message comes up.
I get an error message that displays basically all the arguments for Eclipse, and a file like the one I posted appears in the Eclipse folder. The splash window stays up doing nothing, and I have to ctrl + alt + del out of it.
I'm using Java 5 (1.5) with Eclipse 3.1. You are definitely allowed to do that.
It is possible that the message isn't being misleading and it is a memory issue. There is a switch to tell Eclipse to start with more memory. I don't recall the setting, but it is in the readme. I needed to use that on Eclipse 3.0 because my computer was low on physical memory.
Any time you get that sort of failure, you have, by definition, uncovered a bug in the VM. Generally the easiest way to resolve a problem like that is to switch to a different VM - either a different release and/or a different VM provider (like IBM's Jikes).
It looks like a text string overwrote your stack, which would DEFINITELY be a bug in the VM, since Java's designed to be immune to stack issues. Ideally, even when executing buggy Windows system code. I'm not very forgiving some times.
You MIGHT be able to tweak parameters such as heap sizes, Windows system code fixes and the like and make it go away.
Customer surveys are for companies who didn't pay proper attention to begin with.