Community
Participate
Working Groups
Build Identifier: Helios Release: 20100610-0636 When I selected a number of characters in the CSS editor Eclipse hang with 100% CPU and didn't come out of the freeze. Earlier it did come out of the freeze, but only after a minute or so. When I really try to reproduce I couldn't get it to fail. I have no logging of the incident and also no recording of anything in the Event Viewer in Windows. BTW: I use Eclipse IDE for Java EE Developers. Reproducible: Sometimes Steps to Reproduce: 1. Open css file in CSS editor 2. Select (with keyboard) some text
Moving to WTP
Could you attach sample file and provide some more detail on how to reproduce it?
Well, that's the problem. If I could reprocude it I definitely would attach a file and explain it in more detail, but I can't do it on purpose. When I try to reproduce the problem Eclipse won't freeze. I remember a freeze a couple of days ago when I selected (shift+end) on a line which looked like this: div.scroll-document p {font-size: 1em; line-height:1.2; padding-left: 10px; width:auto;} I started my selection just before a semicolon and pressed shift+end.
Created attachment 173269 [details] CSS file I had problems with This is the file I had eclipse freeze on several times.
I tried to reproduce it many times, on file you have provided, but failed to get hang.Did you face this problem again?We can resolve it for now, feel free to reopen if you face similar issue again.
I haven't been able to reproduce it in at least a couple of weeks. I seem to remember a freeze just after I downloaded and installed to final release of Helios, but that happened only once. Let's call it resolved :-)
Thanks for your help with this, Martin and Rakesh. Resolving based on their findings.
This bug is not resolved for sure. It keeps happening to me since I updated to Helios. I use Eclipse at work for web development and it has become unusable: it hangs 4 or 5 times a day. It's very easy to reproduce: you only have to select some text in CSS editor; it eventually will hang. I tried updating to last nightly build (Version: Helios Release Build id: 20100617-1415) but no luck. I am including a capture of the open file and the selected text of one of those hangings. This is rendering Eclipse unusable for me. Never happened with previous version.
Created attachment 181615 [details] Selected text when Eclipse hung
(In reply to comment #8) > This bug is not resolved for sure. I worked for weeks without the problem, but last week it did happen to me once. Eclipse hang as I selected maybe 10 characters. The only option I had was to kill the process.
Still not able to reproduce :(. I see that in the capture that file is dirty. Were you trying to move the selected portion? In that case it appears similar to Bug 326411.A stacktrace or steps to reproduce would be very helpful.
(In reply to comment #11) > Still not able to reproduce :(. I see that in the capture that file is dirty. > Were you trying to move the selected portion? In that case it appears similar > to Bug 326411.A stacktrace or steps to reproduce would be very helpful. I've had a couple of hungs in a couple of hours. I'm attaching another capture of the last one. This time it was selecting the text of a comment. Yeah, the code is "dirty"; they make me write the tags uppercase, maybe it has something to do. By the way, I select text with mouse, not with keyboard. How can I send a "stacktrace"? Reproducing it is very simple: just select some text :(
Created attachment 181806 [details] Selecting text in CSS editor makes Eclipse hang
(In reply to comment #12) > How can I send a "stacktrace"? http://wiki.eclipse.org/How_to_report_a_deadlock Whether it's a deadlock or just obnoxiously slow, a stack trace helps us understand what's taking so long.
(In reply to comment #14) > (In reply to comment #12) > > How can I send a "stacktrace"? > > http://wiki.eclipse.org/How_to_report_a_deadlock > > Whether it's a deadlock or just obnoxiously slow, a stack trace helps us > understand what's taking so long. Pere or Martin, I know it's been quite some time, but have you been able to use this wiki article to report a stack trace? Or are you still seeing this problem?
(In reply to comment #15) > Pere or Martin, > > I know it's been quite some time, but have you been able to use this wiki > article to report a stack trace? Or are you still seeing this problem? Personally I haven't seen this problem in the newest version of Eclipse. I have been using Indigo for some time now and have never seen this problem again.
Thanks for getting back to us, Martin. This possibly was solved indirectly. If it hasn't been, following the instructions in comment 14 to get a stacktrace would be invaluable.
