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 255113 - Deadlock NetBeans startup splash screen -- Starting modules...
Summary: Deadlock NetBeans startup splash screen -- Starting modules...
Status: RESOLVED DUPLICATE of bug 255095
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-09 05:44 UTC by MackSix
Modified: 2015-09-10 05:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread Dump (43.82 KB, text/plain)
2015-09-09 05:44 UTC, MackSix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MackSix 2015-09-09 05:44:58 UTC
Created attachment 155995 [details]
Thread Dump

I am using the Zip Java EE version of NetBeans. I noticed this after installing the C/C++ plugin on the latest dev version. When I have this and some other plugins installed (C/C++, PHP, Python) it happens more frequently. With the extra plugins installed, it happens about 20%-30% of the time restarting NetBeans 0 - 5 seconds after shutdown. It seems to occur more frequently after browsing the Options panels of the extra plugins, waiting for C/C++ tool validation to complete, then shutdown and restart. 


The deadlock occurs at the startup splash screen when it indicates "Starting modules..."

See attached thread dump. "Found 1 deadlock."


Product Version: NetBeans IDE Dev (Build 201509080002)
Java: 1.8.0_51; Java HotSpot(TM) 64-Bit Server VM 25.51-b03
Runtime: Java(TM) SE Runtime Environment 1.8.0_51-b16
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)


It happens with JDK 1.8.0_60 too.
Comment 1 Jiri Kovalsky 2015-09-09 20:20:10 UTC
Reassigned for further evaluation.
Comment 2 Tomas Hurka 2015-09-10 05:35:50 UTC

*** This bug has been marked as a duplicate of bug 255095 ***