[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-651) NullPointerException under MarkSweep Garbage Collection

[Steve Davidson (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-651?page=comments#action_12370937 ] 
            
Steve Davidson commented on JBIDE-651:
--------------------------------------

Greetings.
I would suspect either the NullPointerException in org.jboss.ide.eclipse.as.core.packages.ProjectArchiveStorer.loadArchiveFrom is not being handled properly by the JVM, or what is causing the NPE is causing the JVM crash.

I have seen cases where a flaw in the Application layer can cause the JVM to crash, although fewer in 1.4 than 1.3.

In the meantime, switched to the Incremental GC, to see if that's any more stable.

-Steve



> NullPointerException under MarkSweep Garbage Collection
> -------------------------------------------------------
>
>                 Key: JBIDE-651
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-651
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: JBoss Tools Core
>         Environment: SuSE 10.1
> Linux gorky 2.6.16.27-0.9-default #1 Tue Feb 13 09:35:18 UTC 2007 i686 i686 i386 GNU/Linux
> java -version
> java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
>            Reporter: Steve Davidson
>         Assigned To: Marshall Culpepper
>
> java.lang.NullPointerException
>         at org.jboss.ide.eclipse.as.core.packages.ProjectArchiveStorer.loadArchiveFrom(ProjectArchiveStorer.java:29)
>         at org.jboss.ide.eclipse.as.core.packages.ProjectArchiveStorer.getArchiveFor(ProjectArchiveStorer.java:24)
>         at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.getTopPackage(JstPublisher.java:146)
>         at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publish(JstPublisher.java:101)
>         at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:88)
>         at org.jboss.ide.eclipse.as.core.server.stripped.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:89)
>         at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
>         at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
>         at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
>         at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
>         at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
>         at org.jboss.tools.jst.web.ui.action.server.RunServerJob.run(RunServerActionDelegate.java:155)
>         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> #
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> #  SIGSEGV (0xb) at pc=0x68c4376d, pid=4119, tid=3077134000
> #
> # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode)
> # Problematic frame:
> # C  [libxpcom.so+0xc976d]  _ZN13nsCOMPtr_baseD2Ev+0x13
> #
> # An error report file with more information is saved as hs_err_pid4119.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> /usr/local/bin/eclipse: line 3:  4119 Aborted                 ./eclipse $ECLIPSE_OPTS -data /home/$USER/projects $@
> Eclipse.ini file;
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 128M
> -vmargs
> -Xms256m
> -Xmx768m
> -XX:MaxPermSize=256m
> -XX:PermSize=128m
> -XX:+UseConcMarkSweepGC
> -Dosgi.bundlefile.limit=200
> -Steve

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira