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 197344 - NetBeans freezes when I use auto-complete
Summary: NetBeans freezes when I use auto-complete
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P2 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-01 23:08 UTC by OceanWind
Modified: 2011-04-26 16:43 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread Dump for autocomplete problem (215.71 KB, text/plain)
2011-04-22 17:42 UTC, sbvice
Details

Note You need to log in before you can comment on or make changes to this bug.
Description OceanWind 2011-04-01 23:08:13 UTC
Selecting an autocomplete option while coding — using either the mouse or arrow/enter keys — causes NetBeans to freeze up. It goes into some kind of process, and I have to force quit the application.

Product Version = NetBeans IDE 6.9.1 (Build 201011082200)
Operating System = Mac OS X version 10.6.7 running on x86_64
Java; VM; Vendor = 1.6.0_24
Runtime = Java HotSpot(TM) 64-Bit Server VM 19.1-b02-334
Comment 1 Marian Mirilovic 2011-04-04 07:47:03 UTC
Could you please generate thread-dump at time of freeze, attach it here and reopen ? Thanks in advance.
http://wiki.netbeans.org/GenerateThreadDump
Comment 2 sbvice 2011-04-22 17:42:27 UTC
Created attachment 107905 [details]
Thread Dump for autocomplete problem
Comment 3 sbvice 2011-04-22 17:43:03 UTC
I'm having the same problem. I have attached my thread dump
Comment 4 Dusan Balek 2011-04-26 08:11:26 UTC
Could you please attach the Java thread dump and/or NB profiler snapshot (http://wiki.netbeans.org/GenerateThreadDump)? Thanks.
Comment 5 OceanWind 2011-04-26 16:43:46 UTC
I think this issue arises when NetBeans pushes the available RAM limit on the machine. I haven't encountered it again since I reported it (at that time, it had happened 4-5 times in a row), but when it happens again, I'll send you a Java dump. Hopefully the dump submitted by sbvice gives you what you need to know to work with this.

Thanks.