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.
[ BUILD # : 200807310201 ] [ JDK VERSION : 1.6.0_07 ] When invoking auto complete (CTRL+SPACE) for attributes or attribute content on a JSP tag the system freezes for 10-15 seconds and the whole system becomes completely unresponsive. This also occurs when saving after making changes to a JSP file. Stacktrace attached.
Created attachment 66386 [details] Stacktrace
Also tested on build 200808010201 On top of that the whole system froze again when I was working on a JSP page. This time I had to kill the process from the task master. Stacktrace attached. I'd now consider the JSP editor to be P1 as the performance is so bad that it cannot be used efficiently.
Created attachment 66398 [details] Another stack trace
20080802. Create web app: if I add JSF framework autocomplete after < is about 5sec. on my computer if I add Struts it's about 10sec. for web app w/o framework or with other frameworks autocomplete is ok.
With 200808021401 the performance seems to be even worse. Now I can barely do anything (opening a file, editing, auto-completing) without CPU going to 100% and the whole system freezing. Also I noticed that it takes longer for NetBeans to recognise the tags used in existing JSP files (by recognising I mean highlighting the tags with bold blue rather than normal blue).
I tried to reproduce (on Mac) the issue on the latest build in a web project with moderate number of jsps. Regardless there are any frameworks in the project the completion speed is approximately the same (almost instant). Web project reparse is also fast. The threaddumps shows mostly some disk activity triggered from the JSP parser. Can you please confirm your web project is located on local filesystem? There might be some timestamp issues on remote FS which may lead to similar problem. Can you also confirm you are using Windows XP? Could you try to run netbeans with a new userdir? Can you reproduce the problem on a brand new web project with the frameworks you mention added? If not, how much files (JSPs, java classes) does your project contain? BTW is the problem regression of the 200807310201 build? Did it work fine with older ones? Please try to answer the questions quickly since we need to resolve all P1 issues ASAP. Once we are able to reproduce, we can provide some fix quickly. Can someone from our QE try to reproduce the issue on a windows machine? Jindro? Thanks.
The problem has been there since I started using daily builds (20080730). Operating System: Yes, I'm using Windows XP File System: I'm using local storage only For all builds I've started with a clean userdir Please check thread on the the NetCAT mailing list with the subject: "[65cat][j2ee] JSP editor performance degraded to a point where it is unusable". Many users seems to have this problem. I should note that I haven't tested it with a NetBeans Web Project, but instead as a Maven Web Application project. The project I'm testing it on is fairly small. Approx. 10 JSP pages and 10 backing beans.
Furthermore the system also freezes when invoking source formatting.
The issue may be caused by recent fix of issue 139087. QE is trying to reproduce on older builds... As for the formatting problem, there is a P2 issue 142011.
Doesn't seem to be the same as 142011 as the formatting eventually finished but only after 10-15 seconds (sometimes more). I will try todays build and see if the issue has been fixed.
I'm not able to reproduce the same stacktrace as the attached one, but I'm attaching different one. It's reproducible on latest build. Cpu start running for 100% few seconds after doing edit action in JSP file.
Created attachment 66480 [details] threaddump
I can reproduce the same issue as Jindra with JSPWiki project. If I edit a JSP file in the WP, the parser run is very fast. But if I invoke a jsp completion there is about 4 seconds delay with a high CPU activity - the parser accesses some project jar files as is visible from jsedek's last attachement. Reassining to jsp parser for more evaluation. Tere were two changes recently - one in the mentioned issue 139087 and one done by Petr Hejl in web apps classloading, which could possibly cause this. OTOH the stacktraces originally reported by big_al are different.
I'm looking at it.
The cause of this issue is the fix of the issue #128360 - I will backout that fix and try to solve it a bit differently.
Fixed in trunk - could someone verify please? I would backport it to the beta clone as well. Thanks. http://hg.netbeans.org/main?cmd=changeset;node=46d26934af9d
It seems to have improved, although I haven't been able to verify it with my Maven projects (as Maven J2EE support seems to be broken in the latest build.
If you just backed out a recent change than there is not much need for a verification, no?
Integrated into 'main-golden', available in build *200808060201* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/46d26934af9d User: Tomas Mysik <tmysik@netbeans.org> Log: #142684: [65cat] JSP editor sluggish on auto complete and save Backed out changeset 3a5b4ac5d752
> If you just backed out a recent change than there is not much need for a verification, no? It is because I'm not really sure that this is the only cause of this issue - I verified using profiler but also need feedback from real, everyday work.
NetBeans IDE Dev (Build 20080806033315) verified.
Transplanted to release65_beta clone. http://hg.netbeans.org/release65_beta/rev/c78081c1fa73 http://hg.netbeans.org/release65_beta/rev/7b21be3e5a13