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 &lt;/pg:item&gt; 
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