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 197309 - IDE slow after JavaScript File opened and closed
Summary: IDE slow after JavaScript File opened and closed
Status: RESOLVED DUPLICATE of bug 197534
Alias: None
Product: editor
Classification: Unclassified
Component: Painting & Printing (show other bugs)
Version: 7.0
Hardware: PC Windows Vista
: P2 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-04-01 07:30 UTC by bht
Modified: 2011-06-08 11:27 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Test JavaScript File (234.01 KB, text/x-c)
2011-04-01 07:30 UTC, bht
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bht 2011-04-01 07:30:42 UTC
Created attachment 107422 [details]
Test JavaScript File

After a simple but large one line JavaScript file is opened and closed in the editor, the IDE becomes very slow.

For example, keyboard navigation the tree in the project explorer is slow. I cannot detect high CPU usage.

The only solution I found is to re-start NetBeans.

Please refer to the attached test file.
Comment 1 bht 2011-04-18 09:14:38 UTC
A script file containing only a single line which contains a single variable.

Hopefully fixing this as soon as possible will have the side effect of solving other problems.
Comment 2 Marek Fukala 2011-05-17 13:52:41 UTC
Reproducible in current dev build. The editor view hierarchy is painting really loooong. Some of the view hierarchy code execution is done in EDT, some in ViewHierarchy-Region-Rebuilding thread. Apparent problem of the editor view hierarchy infrastructure. Though the file structure is not typical (250kB long line), in javascript is not that uncommon.
Comment 3 Miloslav Metelka 2011-05-24 14:03:45 UTC
I will implement more lazy initialization of views for long lines which should improve the situation.
Comment 4 Miloslav Metelka 2011-06-08 11:27:09 UTC
Marking as dup since issue #197534 should cover this case too.

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