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 113910 [details] ide snapshot Steps to reproduce: - create new Java Web application (Java EE6 Web, GlassFish 3.1.1) - edit index.jsp and save it => saving takes "long" time (about 2s) Product Version: NetBeans IDE 7.1 (Build 201112062100) Java: 1.7.0_02; Java HotSpot(TM) Client VM 22.0-b10 System: Linux version 3.0.0-13-generic-pae running on i386; UTF-8; en_US (nb)
I am experiencing this as well, although my snapshot is a bit different. Will attach it.
Created attachment 115086 [details] Profiler snapshot
my Version is 7.1 Build 201112071828 Java 1.6.0_24, Debian 6, Im also experiencing this issue, with Java Web Application Project, JSP pages with tomct 6 Server. Tried with With Windows 7 OS ,the Same issue was observed. whereas Version 7.0 , the same project in the same location did not have this issue.
Changing priority to P2 so we don't forget about it. This is pretty annoying.
I used Netbeans 7.1 on MacOSX Lion( SSD ), Windows 7 32Bit( ssd ), Windows 2008R2 64bit The Same issue was observed.
same issue here Product Version: NetBeans IDE 7.1 (Build 201112071828) Java: 1.6.0_30; Java HotSpot(TM) 64-Bit Server VM 20.5-b03 System: Windows 7 version 6.1 running on amd64; Cp1252; en_SG (nb) this bug is damn annoying
A quick profiling run shows the trouble is coming from org.netbeans.modules.web.core.jsploader.TagLibParseSupport public JspParserAPI.JspOpenInfo getCachedOpenInfo(boolean preferCurrent, boolean useEditor) this method is called multiple times in a row upon I Ctrl+S then I changed the implementation to bypass the original processing, and straight away return new JspOpenInfo(false, "UTF-8"); which this is a bit brute force, but it does seem to work now my jsp editor is back to normal again
I am glad it works for you, however this change is obviously not correct for non-English users. So we will need a better fix.
I attached a thread-dump generated by the NetBeans self-sampler during high CPU activity while editing a JSP file. It seems there are far too many threads named "JspFoldManager" running (16). FYI, I had just three JSP files open.
Created attachment 115894 [details] thread-dump
I also am observing this problem. Netbeans 7.1.1 + tomcat that comes with it [7.0.22.0]. Ubuntu 11.10, with Oracle official JDK6r31 in /usr/lib/jvm/jdk1.6.0_31 64-bit Core-i7, 12G memory. Every time I hit "save" while editing a JSP file, I have a second or two's wait during which the GUI appears locked up.
I can confirm this is still happening in Netbeans 7.1.1, JDK 7u3.
I used Netbeans 7.1(Build 201112071828),Java 1.7.0(Java HotSpot(TM) Client VM 21.0-b17) on Windows 7 64Bit( ssd ). The Same issue was also observed.
Encoding can be read also from the file content which was impossible to get using FO inputStream in cases that the file was open for write. I'm getting the text from the editor and it looks all right. Fixed in web-main #40d514a9762a.
Integrated into 'main-golden', will be available in build *201204260400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/40d514a9762a User: Martin Fousek <marfous@netbeans.org> Log: #206064 - Slow saving JSP and Tag file
verified, thanks Product Version: NetBeans IDE Dev (Build 201204260400) Java: 1.7.0_04; Java HotSpot(TM) Client VM 23.0-b21 System: Linux version 3.0.0-17-generic-pae running on i386; UTF-8; en_US (nb)