- This topic has 12 replies, 4 voices, and was last updated 17 years, 12 months ago by
.
-
Posts
-
I have noticed that the JSP editor is slow under the following conditions:
– Large JSP (1500+ lines)
– Scrolling to the right OR editing, highlighting, etc. when the editor is already scrolled to the right
– Editing near the top of the fileSymptoms:
– Scrolling to right redraws slowly and pegs the CPU near 100%
– Character echo lags behind typing by several seconds and also pegs the CPU between charactersThe larger the file and the closer to the beginning of the file you are, the slower the editor is. Once you get near the end of the file (no matter how big the file is), the lag is nearly gone. With the editor scrolled all the way to the left, there is no lag no matter how big the file or how far down. It’s only once the cursor hits the right edge and tries to scroll horizontally that the slowness occurs.
Environment: Windows XP, Eclipse 3.2, MyEclipse 5.0.1
Hope this gives you all the info you need. I can provide a sample file if needed.
Thanks
– EricEric,
How long is the problomatic line? We had another report from a user with “long lines” that it is painfully slow as well and filed an issue for investigation. I’ll add your comments to that issue.@support-rkalla wrote:
How long is the problomatic line?
Anything that causes the editor to need to scroll. Interestingly, if I leave the editor in a “normal” state and edit a line off the edge of the page, I observe the described behavior. If I double-click the editor heading to “maximize” it, then edit the same point in the line (but no longer off the edge of the page), the performance is fine.
@support-rkalla wrote:We had another report from a user with “long lines” that it is painfully slow as well and filed an issue for investigation. I’ll add your comments to that issue.
Muchos gracias. I’ll second the “painfully slow” description. In my case, it certainly negates the value of the JSP editor.
i have the same problem, and i’m using only WTP 1.5, without MyEclipse IDE. I think the problem is in jsp editor.
Ando thanks for the heads up, we’ll follow up with the WTP team to see if they can work out the kinks on their end.
Did anything ever come of this?
I’m having similar problems with a nasty JSP I’ve inherited that is both ‘long’ and ‘wide’. If I maximize the editor, I can edit lines without a problem. However, If I horizontally scroll and then edit the same line – the CPU hits 100% and the editor runs very slowly indeed.
Cheers,
Paul
*** Date: Tue Nov 07 16:50:41 GMT 2006 *** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_07 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 5.0 GA Build id: 20060805-5.0-GA *** Eclipse details: Eclipse SDK Version: 3.2.1 Build id: M20060921-0945 Eclipse Graphical Editing Framework Version: 3.2.0.v20060626 Build id: 20060627-0816 Eclipse Platform Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx Build id: M20060629-1905 Eclipse RCP Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq Build id: M20060629-1905 Eclipse Java Development Tools Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC- Build id: M20060921-0945 Eclipse Plug-in Development Environment Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG Build id: M20060921-0945 Eclipse Project SDK Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ Build id: M20060921-0945 Eclipse startup command=-os win32 -ws win32 -arch x86 -launcher C:\Java\Eclipse3.2\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata 17a0_80 -clean -vm C:\WINDOWS\system32\javaw.exeDoes anybody know if the bug was fixed in the latest release? (myeclipse 5.1)?
I’ve tried some patches for wtp 1.5.0 release, but didn’t work better 🙁MyEclipse 5.1 is not based on WTP 1.5.2 (latest stable) so if your patches made it into the WTP release stream it’s possible they are in 5.1 now. We’ve seen some good performance improvements across the board so far.
It does seem to be a bit faster… (I’ve taken to using the myEclipse JSP editor now as the visual one is unusable for me with these ‘long and wide’ pages)
However, whenever I try to horizontally scroll the editor panel, the CPU still hits 100% for about 5 mins and the PC freezes.
I have tried to ‘lengthen’ the pages where possible – but it’s an arduous task so I’ve taken to giving the JSP editing to my colleague who uses netbeans and hasn’t got the same problem – plus, it saves me a bit of work 🙂 Il’ll be glad when it’s fixed though – JSP editing is currently off limits for me…
Cheers,
Paul
*** Date: 21 November 2006 09:14:50 o'clock GMT ** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_09 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 5.1.0 GA Build id: 20061111-5.1.0-GA *** Eclipse details: MyEclipse Enterprise Workbench Version: 5.1.0 GA Build id: 20061111-5.1.0-GA Eclipse Graphical Editing Framework Version: 3.2.0.v20060626 Build id: 20060921-1617 Eclipse Platform Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx Build id: M20060629-1905 Eclipse RCP Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq Build id: M20060629-1905 Eclipse Java Development Tools Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC- Build id: M20060921-0945 Eclipse Plug-in Development Environment Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG Build id: M20060921-0945 Eclipse Project SDK Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ Build id: M20060921-0945 Eclipse Graphical Editing Framework Version: 3.2.1.v20060921 Build id: 20060921-1617 Eclipse startup command=-os win32 -ws win32 -arch x86 -launcher C:\Java\Eclipse3.2\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata d30_80 -product com.genuitec.myeclipse.product.ide -vm C:\WINDOWS\system32\javaw.exeThe only way I can find around this is to open all .jsp’s in the text editor (even the JSP editor hogs the CPU) – i’m obviously making more mistakes in the code – but at least I can work. Hopefully this proves that the problem is firmly within the JSP editors as the rest of the environment is running very well indeed EG integrated JBOSS, checking in and out of source control, Java class editing etc
Cheers,
Paul
Paul,
I’m sorry this is still causing a headache for your team. I will make a note to the developers that this is still not fixed and mark it important for them.
