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 252013 - Editor froze up - had to be killed
Summary: Editor froze up - had to be killed
Status: RESOLVED DUPLICATE of bug 251825
Alias: None
Product: java
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.1
Hardware: PC Windows 8 x64
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-23 09:34 UTC by akobberup
Modified: 2015-05-14 14:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (30.45 KB, text/plain)
2015-04-23 09:34 UTC, akobberup 		Details
Screenshot of editor in rigor mortis (12.36 KB, image/png)
2015-04-23 09:36 UTC, akobberup 		Details
messages.log (389.77 KB, text/plain)
2015-04-23 09:38 UTC, akobberup 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description akobberup 2015-04-23 09:34:56 UTC 
Created attachment 153316 [details]
Thread dump

My ide sudently froze up - perhaps during codecompletion, and i had to kill it.

Product Version: NetBeans IDE Dev (Build 201504201004)
Java: 1.8.0_31; Java HotSpot(TM) 64-Bit Server VM 25.31-b07
Runtime: Java(TM) SE Runtime Environment 1.8.0_31-b13
System: Windows 8 version 6.2 running on amd64; Cp1252; da_DK (nb)
Comment 1 akobberup 2015-04-23 09:36:18 UTC 
Created attachment 153317 [details]
Screenshot of editor in rigor mortis
Comment 2 akobberup 2015-04-23 09:38:49 UTC 
Created attachment 153318 [details]
messages.log
Comment 3 akobberup 2015-04-27 08:23:07 UTC 
I Have gotten this a few times now - and actually if i just wait, it will come alive again..
Here is the latest slowness report i made, and i think its the same issue:

http://statistics.netbeans.org/analytics/exception.do?id=776333
Comment 4 Tomas Hurka 2015-05-14 14:51:21 UTC 
This looks like duplicate of bug #251825.

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