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.
Created attachment 162689 [details] javascript2-all-in-one-issues.zip Hello, i'm using NetBeans for JS and Java devlopment. Thanks for new JS-related staff introduced in Release 8.2, but implementation has numerous performance issues - project is loaded for extremely long time and editing of files is laggy (while editing JS libraries of 10K lines). I've self-profiled Netbeans and applied some hot fixies in my local dev-built. Most of the performance issues seem to be fixed - the rest does not look to be a show-stopper and do not look to be easily fixable by external person. Anyway - the build i have locally seems to be rather OK for me. So ... - there are 20+ issues in attached zip each in separate file - the most severe typically go first. Each sub-folder includes screenshots from self profiler for the issue to be fixed. Also subfolder may or may not contain some description. - zip also includes an all-one-patch - i was going to make individual patch per-issue, but this appears to be extremely time consuming for me Note: it seems that enabled 'View -> Show Breadcrumbs' cause much more frequent reparsing of sources and self-profilier better shows hotspots in this case. Patch relies on LruCache file, the new one i've added into 'openide.util\src\org\openide\util' - it is provided as separate file and already included in the patch referenced in another issue (https://netbeans.org/bugzilla/show_bug.cgi?id=268744 - i'm not sure if it will be aplied). Attachment also includes test project with few 'real' files which provide enough load to easily reproduce issues.
Note: Patch is made on-top of this revision http://hg.netbeans.org/main/rev/10cc566d91aa Which i beleive is last commit for Release 8.2
Thanks for this. I will go throuh one by one, evaluate and create separate issue for this.
Created attachment 162702 [details] js-patches.zip
I'm using Git for local development - I've attached patches generated from Git for more granular changes (not sure if it is mercurial-compatible). This may be more helpful for "one by one" analysis.