This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 238865

Summary:	Couple ergonomics tests failed due "Forked Java VM exited abnormally"
Product:	platform	Reporter:	Maksim Khramov <mkhramov>
Component:	JDK Problems	Assignee:	Antonin Nebuzelsky <anebuzelsky>
Status:	RESOLVED WONTFIX
Severity:	normal	Keywords:	TEST
Priority:	P3
Version:	7.3.1
Hardware:	Sun
OS:	Solaris
See Also:	https://netbeans.org/bugzilla/show_bug.cgi?id=215153
Issue Type:	DEFECT	Exception Reporter:

Description Maksim Khramov 2013-11-27 10:46:52 UTC

Running Java(TM) SE Runtime Environment 1.7.0_45 b18 (1.7.0_45-b18) 
and NB 7.3.1 on Solaris 11 Sparc

Listed tests afiled at BeforeFirstTest with  error message: 
Forked Java VM exited abnormally.

org.netbeans.modules.ide.ergonomics.CachingPreventsLoadingOfModuleManifestsTest
org.netbeans.modules.ide.ergonomics.fod.FeaturesOffDemandTest
org.netbeans.modules.ide.ergonomics.fod.FoDUpdateUnitProviderTest
org.netbeans.modules.ide.ergonomics.fod.ParseXMLContentTest
org.netbeans.modules.ide.ergonomics.fod.ProjectDuplicatedTest
org.netbeans.modules.ide.ergonomics.fod.ProjectEnableFailureTest
org.netbeans.modules.ide.ergonomics.fod.ProjectFalsePositiveTest
org.netbeans.modules.ide.ergonomics.fod.ProjectOnDemandTest
org.netbeans.modules.ide.ergonomics.fod.ProjectOpenTriggersAddOnsTest
org.netbeans.modules.ide.ergonomics.fod.ProjectRejectedTest
org.netbeans.modules.ide.ergonomics.fod.ProjectWithDependenciesTest

Comment 1 Maksim Khramov 2013-11-27 11:00:56 UTC

Same issue affects also these tests:
org.netbeans.modules.netbinox.IntegrationTest
org.netbeans.modules.netbinox.LogReaderServiceTest
org.netbeans.modules.netbinox.NetigsoHasSAXParserTest
org.netbeans.modules.properties.PropertiesEncodingInMimeLookupTest
org.netbeans.modules.xml.InstanceDataObjectInXMLTest
org.netbeans.spi.debugger.ui.EngineComponentsProviderTest

Comment 2 Jaroslav Tulach 2013-11-29 16:47:02 UTC

Should not you rather report the bug to the JDK team? You know, crashing JDK is always a JDK problem.