- This topic has 41 replies, 9 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
I should add that the “backwards typing” mentioned here is not *THE* backwards typing problem; I ran into that last year. What occurs in this case is an intermittent misplacing of the cursor. If I type very slowly the effect is avoided.
Your setup looks fine, can you adjust your startup arguments to look like the ones outlined here and see if that helps:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.htmlNot really any change. If it helps at all, there is lots of yellow underlining, but it’s always moving around, even when I stop typing. Even now I can see the yellow markers on the right edge of the editor are flashing.
Oh, and every time this happens, eclipse ramps up its memory usage (from ~100 to ~500MB), and won’t shut down. I have to force the java process to quit.
This is the JSP editor you are having trouble with correct? I would be interested in the screenshots as well as a test page AND directions on how to reproduce the problem. For example, send me a test JSP page and tell me “go to hte 2nd paragraph and start typing a really long sentence, be sure to keep the outline view open” or something like that.
If I can reproduce it, I can file it as a bug.
BTW if you can send me this stuff, send it to support@genuitec.com ATTN Riyad, with a link to this thread so I know why I’m getting it.
Good lord, I see the problem with 4.1.1 in spades given your test case. The problem is that the reconciler is being too aggressive, if you use autocomplete and allow it to close your tags for you, and not leave them hanging open like that, it doesn’t need to reevaluate the entire file every key stroke (that’s a workaround, I’m not suggesting that this is *good* behavior). So when I did the same example using autocomplete letting it close the tags and quotes for me, the performance was fine.
Also, when I tried the exact same setup with Eclipse 3.2M6 and MyEclipse 5.0M1 the problem was almost gone. The obsessive “updating outline” doesn’t occur and the insane memory usage didn’t happen either, although my processor did stay busy for a few seconds after I stopped typing.
Additionally using autocomplete to close the tags was smarter and helped the issue even more such that it wasn’t an issue. So it seems we are going in the right direction, I do have to appologize for the current behavior, I wasn’t aware of the worst-case scenario like this. Thanks for your help in digging deeper with your example.
I am also affected by this, Eclipse hangs for 20-30 secs sometimes when I edit a jsp page, and the yellow underlining is blinking. The progress bar shows alot of “Update outline”. Is there any workaround to this? It is really slowing me down and is amazingly frustrating.
so, what is the conclusion….do i have to upgrade to beta? I’ve read through this forum and am still not sure how to resolve this issue. Sorry for being dense if thats the case
Honestly I’m not sure, the folks I’ve asked to try it didn’t respond. As I mentioned in my post a few posts up, it seemed quite a bit better *for me*. But no, I would never encourage our users to move to a beta release for production work. My offcial stance on the subject is to “try and work around it or live with it until 5.0 has a stable release”, but if you happen to not listen to me and install the Miletstone 1 release to a clean dir along with a clean Eclipse 3.2M6 or M7 install to a clean dir, I wouldn’t stop you and we would still try and support your work. Although if you run into bugs ti’s hard to provide workarounds as it is a beta.
I might suggest dual installs fi the problem is REALLY bad.
