Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338367

Summary:

Checkout causes RIM crash

Product:

z_Archived

Reporter:

Joerg Reichert <joerg83reichert>

Component:

Remus

Assignee:

Tom Seidel <tom.seidel>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
JVM Stacktrace under MacOS	none

Description Joerg Reichert

2011-02-28 02:50:57 EST

Build Identifier: RCP-TRUNK-118

I set up a new workspace and checkout existing files from a remote file repository, but certain files causes RIM to crash (and restart with this workspace is not possible anymore). I guess this is due to checking out information units that required information unit plugins that are not installed in the current RIM instance. The following stacktrace may related to this error, but I am not, as at some crashes nothing is logged:

!ENTRY org.eclipse.core.resources 4 2 2011-02-27 18:02:01.969
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.remus.core.edit.EditingUtil.getObjectFromUri(EditingUtil.java:165)
	at org.eclipse.remus.core.edit.EditingUtil.getObjectFromFile(EditingUtil.java:198)
	at org.remus.infomngmnt.ui.calendar.CalendarBuilder.build(CalendarBuilder.java:81)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Reproducible: Always

Comment 1 Tom Seidel

2011-02-28 07:05:09 EST

The problem of the error message is here that after a crash the workspace-data can be corrupt; this is the case if I look at the stack-trace. Nevertheless an exception in Remus doesn't cause a crash, seems to me this is more a general problem. 
However, after a VM crash, there will be (at least in Windows) an error log, called hs_err_pid*.log in the application directory. Could you attach this log file to see the stackframe that caused the crashed? - Additionally I'd recommend to install Remus again and look if this problem persists.

I've filed bug 338403 to ensure that the data can be read after a crash.

Comment 2 Joerg Reichert

2011-03-07 02:57:48 EST

Created attachment 190513 [details]
JVM Stacktrace under MacOS

I cannot reproduce the error under Windows, so it seems to be due to an old version on Mac.