[Mike]

– System Setup ——————————-
Operating System and version: Linux / Redhat 8
Eclipse version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): Y
MyEclipse version: 3.8B2
Eclipse JDK version: 1.4.2_03
Application Server JDK version: 1.4.2_03
Are there any exceptions in the Eclipse log file? Yes

– Message Body ——————————-

Hi,

Not sure if this is the right place for feedback relating to beta releases?

Here is what I am seeing though .. its a bit loose but I can investigate further if you need me to.

When I debug and start stepping through code analysing data objects etc, MyEclipse is regularly crashing, it tends to happen more often the slower I step through. When MyEclipse crashes it disappears off the screen leaving a JVM error, that doesn’t stay up long enough for me to capture it properly.

The .log file does however have some messages but they seem a litlle spurious because they report that one of the the files that is currently in use by the tomcat 5 server and has just been stepped through or is currently being stepped through cannot be found!

I have cut the first few lines ..

!ENTRY com.genuitec.eclipse.core 1 1 Aug 16, 2004 11:26:11.864
!MESSAGE
!STACK 0
java.lang.ClassNotFoundException: com.twosquared.csheta.common.DispatchActionMapping
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:404)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:252)
at org.apache.commons.digester.Rule.begin(Rule.java:200)
at org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:446)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:778)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:823)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:1028)

I was developing the app using the 2.x version of eclipse and have not seem the same issues before.

I hope this is of some use?

[Mike]

the JVM error when it crashes is …

JVM terminated. Exit code=1
/usr/java/j2sdk/bin/java
-cp /usr/lib/eclipse3/startup.jar org.eclipse.core.launcher.Main
-os linux
-ws gtk
-arch x86
-showsplash /usr/lib/eclipse3/eclipse -showsplash 600
-exitdata /usr/lib/eclipse3/eclipse -exitdata f000e
-vm /usr/java/j2sdk/bin/java
-vmargs
-cp /usr/lib/eclipse3/startup.jar org.eclipse.core.launcher.Main

[Riyad Kalla]

Random,
This may be a out of memory problem, but before we decide that, can you create/use an existing (or new) Java project and create some files and start stepping through it in the same fashion and see if Eclipse still dies?

Eclipse 3 requirets ~2x as much memory as 2.1, so you may want to give it a bit more by adding “-vmargs -Xms128m -Xmx256m” to your command line used to start Eclipse and see if the problem clears up.

[Author]

Posts