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.
Frequently, but unpredictably, ide-executor tests (always in core in think? or maybe openide tests too, not sure) will just hang at startup. I will attach the end of a typical core_unit.log showing a hang in testbag_5. Here the process mentioned really exists: PID TTY STAT TIME COMMAND 13202 pts/1 SN 0:00 /space/jdk1.3.1_03/bin/i386/native_threads/java -Djdk.home=/space/jdk1.3.1_03 -classpath /space/src/nb_all/nbbuild/netbeans/modules/ext/ant-1.5.1.jar:/space/src/nb_all/nbbuild/netbeans/modules/ext/ant-optional-1.5.1.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/junit.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/junit-ext.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/boot.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/crimson-1.1.3.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/junit-ext.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/junit.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/regexp-1.2.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/rmi-ext.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/xerces-2.0.2.jar:/space/src/nb_all/nbbuild/netbeans/lib/ext/xml-apis-1.0b2.jar:/space/jdk1.3.1_03/lib/dt.jar:/space/jdk1.3.1_03/lib/htmlconverter.jar:/space/jdk1.3.1_03/lib/tools.jar -Dnetbeans.osenv=/tmp/nbenv.13146 -Dnetbeans.user=/space/src/nb_all/xtest/instance/work/sys/ide -Dnetbeans.home=/space/src/nb_all/nbbuild/netbeans -Djava.security.policy=/space/src/nb_all/nbbuild/netbeans/bin/ide.policy -Xms24m -Xmx96m -Dnetbeans.logger.console=true -Dnetbeans.mainclass=org.netbeans.xtest.ide.Main -Dtest.class=org.netbeans.xtest.AntRunner -Dtest.classpath=/space/src/nb_all/xtest/instance/work/sys/tests/unit/src -Dtest.basedir=/space/src/nb_all/core/test -Dtest.ant.file=/space/src/nb_all/xtest/lib/module_harness.xml -Dtest.target=ide_test_helper -Dtest.reuse.ide=false -Dxtest.home=/space/src/nb_all/xtest -Dxtest.includes= -Dxtest.excludes= -Dtbag.classpath=/space/src/nb_all/xtest/instance/work/sys/tests/unit/src -Dtbag.patternset.include=org/netbeans/core/awt/TabControlTest.class,org/netbeans/core/windows/frames/PerimeterPaneTest.class,org/netbeans/core/windows/UIModeManagerTest.class,org/netbeans/lib/terminalemulator/TermTest.class,org/netbeans/core/projects/FileStatePropertyTest.class,org/netbeans/core/BundleKeysTest.class -Dtbag.patternset.exclude= -Dtbag.testtype=unit -Dtbag.formater=unit -Dtbag.name=JellyTools_compatibility -Dtbag.executor=ide -Dxtest.module=core -Dxtest.attribs=stable -Dxtest.distexec=true -Dtest.exit=true -Dtest.propertyfile=/space/src/nb_all/xtest/instance/work/sys/userdata.properties -Dxtest.workdir=/space/src/nb_all/xtest/instance/work -Dxtest.results=/space/src/nb_all/xtest/instance/results -Dxtest.results.testrun.dir=/space/src/nb_all/xtest/instance/results/testrun_030110-021332 -Dtest.output.redirect=true -Dnetbeans.full.hack=true -Djunit.properties.file= -Dnetbeans.windows=mdi -Dxtest.error.manager=true -Dxtest.timeout=2400000 -Dnetbeans.systemclassloader.patches=/space/src/nb_all/xtest/instance/work/sys/idejars/xtest-junit-testrunner.jar org.netbeans.Main -nosplash kill -QUIT 13202 has no apparent effect; at least no thread dump appears in core_unit.log or anywhere else I can find. Regular kill (-INT) causes the process to terminate and XTest to end the testbag. The ide.log file in fact just ends with this stuff: ------------------------------------------------------------------------------- >Log Session: Friday, January 10, 2003 2:17:10 AM EST >System Info: I have no idea why org.netbeans.core.TopLogging would get this far and then quietly stop. Of course I have only observed such hangs in XTest.
Created attachment 8514 [details] Sample end of log file at time of hang, before killing it
I should mention that this happens to me often enough that I am frequently unable to get the full NB test suite to run to completion at all. So the P2 is justified from my perspective.
We have noticed it in our regular test runs as well. The issue appeared first when we started it after Chirstmas, last monday. Ufortunately, from the XTest point of view, there was no change in XTest harness I'm aware of. On our testing machines we were using old XTest from the first half of December and still noticed these failures since Christmas. So I'm afraid the problem is somewhere else than just in XTest ... Fortunately, Libor was able to capture thread dump from one of our machines and he will attach it to this report. Anyway, from the thread dump it seems we have some deadlock problem (not caused by XTest IMO). Can you look at it a bit closer?
Created attachment 8522 [details] Thread dump
I deleted library for native kill so ignore UnsatisfiedLinkError in attached log. Immediatelly after dumping threads HotSpot error appeared.
Ah, this is for me then. If I could have gotten the deadlock before I could have fixed it much sooner... wonder why kill -QUIT was not working.
I think I fixed it - hard to know for sure, but I more or less understand the cause of the deadlink and I think this patch should help. Reopen if you see it again, of course, preferably with a fresh thread dump. committed Up-To-Date 1.91 core/src/org/netbeans/core/NonGui.java
verified