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.
Since dev build from January 17th, editing of non-Java files in the IDE has become very slow. There is a log of nearly a second between pressing a key and the display of the corresponding character in the editor making it nearly unusable (to me this happens with HTML, XML, properties and plain text files) The Java editor is not affected by this, it is very fast. Windows XP JDK 1.6, NB 6.0 dev build (Jan 17th, 18th and 20th)
How big are the file you are editing? Can you attach some of them here?
The files are not very big. Ranging from a package.html with roughly 500 bytes to a text file with ~32k and XML files between 10K to 100K.
Strange, I've tried a few larger files (HTML, XML) with sizes between 10-30k and it all seemed to be working fine. No noticable lag when typing or navigating in a document. Is there anything else running on the machine? Can you produce a few full thread dumps to see what is running in the IDE (launch the IDE from console and use Ctrl+\ (Linux) or Ctrl+Backspace (Win))? Thanks.
with the build from January 23rd everything is fine again. I'm attaching the thread dump obtained with the build from January 20th anyway (which still showed the poor typing performance)
Created attachment 37680 [details] File containing thread dump
That thread dump is already idle, it was too late. (OK, thread dump is probably not the best analysis tool for ~1s stalls, though when I bound a global window manager key binding to "killall -QUIT java", I could watch sub-second stalls reliably). Now, it still contain some hints. First, there's XML navigation view, which could slow things down if not implemented properly. Next, there's diff sidebar (ran twice? probably not.) which did some computations. And finally, it seems that the file was just opened (first few edits, and the very first especially, can be slower),
Petre, thanks for your analysis. With the dev builds back to normal I am closing this as INVALID. Please reopen, if you think that this deserves more attention and further investigation.