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 256077 - NB freeze on startup
Summary: NB freeze on startup
Status: RESOLVED DUPLICATE of bug 256017
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 8.2
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-21 12:37 UTC by legitalk
Modified: 2015-10-27 09:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (33.85 KB, text/plain)
2015-10-21 12:37 UTC, legitalk
Details
Thread dump, when NB was frozen. (15.30 KB, text/plain)
2015-10-21 12:37 UTC, legitalk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description legitalk 2015-10-21 12:37:06 UTC
Product Version = NetBeans IDE Dev (Build 201510210002)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_60
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.60-b23

Reproducibility: Happens every time

STEPS:
When I start NB, it stared opening projects, and about after 5 minutes freeze, and only thing I can do is to end the process. This is happening since build 201510160002 (this was last build, which was working)
Comment 1 legitalk 2015-10-21 12:37:12 UTC
Created attachment 156872 [details]
IDE log
Comment 2 legitalk 2015-10-21 12:37:43 UTC
Created attachment 156873 [details]
Thread dump, when NB was frozen.
Comment 3 Jiri Kovalsky 2015-10-22 17:41:46 UTC
Again, this thread dump is truncated and badly formatted. Please use VisualVM [1] to generate a new one and reopen. Thanks.

[1] http://visualvm.java.net/download.html
Comment 4 legitalk 2015-10-27 09:55:48 UTC
When I used VisualVM, this is happening:
- NB is running much more slowly
- the problem is not occuring

When I dont use VisualVM, the problem is happening... So?
Comment 5 legitalk 2015-10-27 09:56:45 UTC

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