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 183812

Summary:	[69cat][editor] Extremely slow response when typing. Allows user to get very far ahead of display.
Product:	ruby	Reporter:	esmithbss <esmithbss>
Component:	Editing	Assignee:	issues@ruby <issues>
Status:	REOPENED ---
Severity:	normal	Keywords:	PERFORMANCE
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Thread Dump wile waiting for the IDE to catch up to my typing.

Description esmithbss 2010-04-09 21:16:39 UTC

Product Version = NetBeans IDE Dev (Build 201004090201)
Operating System = Linux version 2.6.32-19-generic running on i386
Java; VM; Vendor = 1.6.0_19
Runtime = Java HotSpot(TM) Client VM 16.2-b04

While I don't type excessively fast, I am consistently able to outpace 201004090201's ability to keep up with my input.  This leaves Netbeans far behind me and generates multiple "Slowness" exceptions.

I'm attaching a thread-dump to help identify what is happening within the system and taking the extra processing time since there were no visual indications of code completion generating dialogs for me.

Comment 1 esmithbss 2010-04-09 21:18:04 UTC

Created attachment 96990 [details]
Thread Dump wile waiting for the IDE to catch up to my typing.

Comment 2 Vitezslav Stejskal 2010-04-10 05:13:38 UTC

The threaddump only shows activity in the EDT, where the slowness detector is saving a profiler snapshot. Could you please also attach those profiler snapshots generated by the slowness detector? Thanks

Comment 3 Vitezslav Stejskal 2010-04-10 05:21:25 UTC

*** Bug 183814 has been marked as a duplicate of this bug. ***

Comment 4 esmithbss 2010-04-10 09:51:21 UTC

Perhaps you can direct me to where NetBeans is saving these profile files. The only profile file I have is one 490MB heapdump.hprof file from an out of memory exception and crash.

Comment 5 David Strupl 2010-10-04 13:48:33 UTC

Something was happening with ruby in the thread dump. Passing to ruby for evaluation.

I suggest to close this report if we cannot get more information as to what was happening when this was happening (some time ago).