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.
This bug was reported on nbusers. I don't have the details of the platform that the user was on. I have just included the message here and will ask on the mailing list for further details. I would be grateful if QA could look into this. To create a similar parse error, create a tag library with a single tag and use it in a JSP without terminating the tag. From: "Glenn R. Kronschnabl" <grk@netquotient.com> To: nbusers@netbeans.org Subject: [nbusers] jsp parsing errors - NetBeans performance killer Date: 31 Jul 2002 12:35:05 -0500 I've noticed in NB 3.4.x that once a ParseException occurs (from ide.log) INFORMATIONAL *********** Exception occurred ************ at Wed Jul 31 12:12:00 CDT 2002 org.apache.jasper.compiler.ParseException: /main/quickfixqu eue.jsp(14,0) Unterminated user-defined tag: ending tag </pg:item> not found or incorrectly nested that NetBeans really drags when you interact with JSP and Java pages. Saving takes a lot more resources (CPU, time), and even switching tabs too. I wish I could quantify it better than that, but I can't. Note that even if you correct the parse error, performance never comes back - you have to restart netbeans (at least that's been my experience). Thanks, Glenn
-J-Dorg.netbeans.modules.web.jspsyntax=-1 switch can help to track JSP parsing in trunk builds
I can not reproduce this - does anyone has any more specific steps to reproduce ? Thanks.
I submitted it, but did so on the basis of a report from nbusers. Perhaps you could fire off an email to the guy whose mail address is in the original description and ask him if he can provide more specifics. Otherwise I agree that we can close it.
I did what Ana suggested, and didn't get a reply. Jason, do you agree we can close this as not reproducible ?
I'm unable to reproduce with the latest Nevada build. I'm able to get the ParseException fairly easy, but I'm seeing no degradation of performance from the IDE. I'm resolving this as WORKSFORME. If we get more information from the user that makes it more easily reproducible, we can re- open.
Verified that it works for me in Nevada build 030213_1.