[dehks]

– System Setup ——————————-
Operating System and version: WinXP SP2
Eclipse version: 3.0
Eclipse build id: I200406251208
Fresh Eclipse install (y/n): yes
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: None
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8 GA
Eclipse JDK version: 1.4.2_03-b02
Application Server JDK version: n/a
Are there any exceptions in the Eclipse log file? No

– Message Body ——————————-

Hi,

I just upgraded to 3.8 GA and found some problems. Opening an editor on XML, JSP, HTML, or XSD files is slow (about 3 secs on my machine). Closing the editor takes about half a second. With Beta 2 there was no appreciable delay opening or closing these files.

This is a clean installation of Eclipse 3.0 SDK, in a clean workspace, with MyEclipse the only third-party plugin. No errors appear in the log. I tried turning off all validation, but it didn’t make a difference.

Steps to reproduce:

1. Create a new J2EE Web Project.
2. Create a JSP file.
-> The editor takes some time to appear.
3. Close it and open it again.
-> It still takes a while to appear.
4. Repeat 2,3 for XML, HTML, JSP, XSD.

I’m looking forward to using the nice new features in 3.8 so I hope there is some kind of workaround for this. As it is, the problem is annoying enough to make me roll back to the previous version.

Cheers,

Dominic.

[Riyad Kalla]

Dominic,
I’ve seen this as well with these brand new editors from WTP… we will continue to fix them up and improve performance but I will add your comments to our performance bug to investigate as I agree 3 seconds is a rediculous amount of time to wait.

[dmiller]

I am having the same problem as well. The ME editors take a very long time to open and close.

I cannot even compile (clean->rebuild) my project without Eclipse crashing (out of memory on a system with 1GB RAM), and it takes *forever* to rebuild. I believe this is because all of the JSP’s are being compiled. I have tried disabling the validation in the project build, but that didn’t do anything.

I am very disappointed with this release of MyEclipse. I expect a GA release to be very stable, but have found just the oposite with 3.8. It takes valuable time to upgrade to a new version, and I don’t appreciate having to downgrade again–even more of my day is wasted. I expect GA versions of the product to be at least as performant as the previous release.

I do like the new editors–they seem to fix the problem with initial tab width. 🙂

[Riyad Kalla]

I cannot even compile (clean->rebuild) my project without Eclipse crashing (out of memory on a system with 1GB RAM), and it takes *forever* to rebuild.

Eclipse 3.0 requires about 2x as much memory as Eclipse 2.1 and when it first came out the most common post in the forums was “Eclipse is crashing, Eclipse is getting OutofMemoryExceptions”. If you haven’t adjusted the amount of ram that Eclipse gets that will greatly improve the situation for you, try adding:
“-vmargs -Xms128m -Xmx256m” to your command line used to start Eclipse, that should make it a happy camper.

I believe this is because all of the JSP’s are being compiled. I have tried disabling the validation in the project build, but that didn’t do anything.

That will disable compilation when saving, but when rebuilding a project all the compilable resources are compiled.

I am very disappointed with this release of MyEclipse. I expect a GA release to be very stable

I hope increasing the memory will help stability issues, other than that please post what other problems you are having. We will get them figured out if it kills us.

I expect GA versions of the product to be at least as performant as the previous release.

That is definately how it should be. As you noticed the editors on ME are completely new so there are some ‘growing pains’ for us to get nailed down just like there was when we first introduced the first version of most of the editors. We do as much testing as we can internally and actually tested/fixed the GA release for a week straight before releasing it… naturally there are project setups, configurations, resources that we never considered and can only be nailed down when real users, like yourself, get their hands on it.

Please hang in there, we will have a quick fix release here soon to fix some of the most annoying bugs that people are finding then do another service release after to futher improve things.

I do like the new editors–they seem to fix the problem with initial tab width. 🙂

Well that’s good 😀

[dmiller]

Thanks for the quick reply.

try adding: “-vmargs -Xms128m -Xmx256m” to your command line used to start Eclipse

This seems to have improved the overall performance of Eclipse. However, I have been using Eclipse 3.0xxx for a long time now with ME and have never experienced such problems with memory. I think this time it’s not Eclipse’s fault.

The XML, JSP, etc. editors still take a long time to open and close, which is very annoying.

I expect GA versions of the product to be at least as performant as the previous release.

That is definately how it should be. As you noticed the editors on ME are completely new so there are some ‘growing pains’ for us to get nailed down just like there was when we first introduced the first version of most of the editors

Maybe you could have introduced the new editors in a beta version rather than a GA release…just a thought.

Why do the syntax highlighting schemes keep changing? Can’t you just pick some good colors and stick with them? I personally don’t like the defaults because the text colors are too light for viewing on a white background. This makes it hard on the eyes for developers who spend a lot of time in an editor.

Are the jstl (and other tag libraries) tag names supposed to be highlighted like html tag names rather than jsp tag names? Example: if I set html tag name color to orange and jsp tag name color to blue “c:if” is orange and “jsp:forward” is blue. Is this how it’s supposed to be? If so, I request it be changed because it is unintuitive.

[Riyad Kalla]

I have been using Eclipse 3.0xxx for a long time now with ME and have never experienced such problems with memory.

Its tricky… some behaviors make the memory usage shoot up and others seem to work fine.

I think this time it’s not Eclipse’s fault.

The new editors are considerable more complex than previous ones, I wouldn’t be surprised if overall ME’s memory requirements is whats causing the OOME. I wouldn’t blame Eclipse either, ME is a huge set of plugins (~138) and that’s a lot of memory that’s required.

Maybe you could have introduced the new editors in a beta version rather than a GA release…just a thought.

It was a gamble for us. Risky? Definately… worth it? Yes… we need to stay ahead of the game.

Why do the syntax highlighting schemes keep changing? Can’t you just pick some good colors and stick with them?

I wasn’t aware of them ‘keep changing’ except in this release they will be totally different… WTP defaults most likely.

I personally don’t like the defaults because the text colors are too light for viewing on a white background. This makes it hard on the eyes for developers who spend a lot of time in an editor.

Were you able to adjust them alright via Window > Preferences > MyEclipse > Editors > JSP > Styles? So far we’ve had a few compliments on it, its hard to say what developers will like. In our next release we are going to make all the text blink and see who likes that 😉

Are the jstl (and other tag libraries) tag names supposed to be highlighted like html tag names rather than jsp tag names?

This certainly does sound wrong, I will check and see if there are still known problems with recognizing the tags in a page, thank you for bringing this to our attention.

[dmiller]

Maybe you could have introduced the new editors in a beta version rather than a GA release…just a thought.

It was a gamble for us. Risky? Definately… worth it? Yes… we need to stay ahead of the game.

I have to disagree with you on this one. I understand that there is an enormous amount of competition, and there is a huge need to be publishing new features a often. But if you publish beta-quality software and call it a final version you’re going to lose your following quickly. I am a paying customer and this does not give me a lot of confidence in your product.

I was able to change the colors. It just adds a lot of extra steps to upgrading when I have to go in and change the colors for each editor.

[Author]

Posts