Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364773

Summary:

Something in querying the registry goes way wrong.

Product:

[Eclipse Project] Platform

Reporter:

kasper T <kasper>

Component:

Assignee:

Platform-UI-Inbox <Platform-UI-Inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

remy.suen

Version:

4.2

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
the only stacktrace i could produce, so the really only clue..	none
the output from process monitor... only on for a few secounds..	none
dump of thread trace..	none
the profiler got this, when it was in dead lock state	none
anouther thread trace, when in dead lock, with more information	none

Description kasper T

2011-11-24 18:35:48 EST

Build Identifier: both 3.6.2.R36x_v20110210 and I20111028-1100 and a lot other versions.

Well as i have studyed this for some hours, i belive it is the main drawing core of Eclipse (i tried with eclipse 4.1 and aptana studio (uses eclipse)), and what i found out was, that somewhere in the drawing process, it suddently decides to use 12-15 % cpu, on.... nothing ... well when i observe in progmon (the windows app to moniter programs), i get milions of milions request in a few secounds (to the regestry). The sad part is, Im unable to tell what it are trying to do, a guess based on the information is some sort of discovery.. or "get main display".
as this is one thing, the problem arrises also when trying to invoke the UI , it is 99% dead, nothing happens. But if you click the menubar, it gets some sort of "air", and can just redraw once ... (im actually running win 8, but i have been doing that for some months, but the problem came from nowhere, or maby when i updated java to 7.1..., but the problem does not occure when using netbeans.)
well i have the stack trace, from eclipse, where it says:
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1708)
at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730)
at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
at org.eclipse.ui.internal.WorkbenchWindow$5.run(WorkbenchWindow.java:860)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
but the trace takes up 269 lines.

Reproducible: Always

Steps to Reproduce:
1.well get windows 8
2.update from java 7 to 7.1
3. for some reason, hope it will get reproduced, not sure, since this might be a special case..

Comment 1 kasper T

2011-11-24 18:36:49 EST

Created attachment 207508 [details]
the only stacktrace i could produce, so the really only clue..

Comment 2 kasper T

2011-11-24 18:42:46 EST

Created attachment 207509 [details]
the output from process monitor... only on for a few secounds..

Comment 3 kasper T

2011-11-25 07:37:58 EST

well, i Thought about the problem and realized that it might be the editor component, because if i dont open any documents, the problem does not happen. (at least for 5 minutes of testing... but as soon as i open a doucment, and start coding, it fails. at random times of cause.

Comment 4 Paul Webster

2011-11-25 08:18:45 EST

When it gets into this state, you can find out what the JVM thinks it is trying to do.  See http://wiki.eclipse.org/index.php/How_to_report_a_deadlock

PW

Comment 5 kasper T

2011-11-25 08:50:29 EST

Created attachment 207531 [details]
dump of thread trace..

when it enters the deadlock state

Comment 6 kasper T

2011-11-25 08:51:14 EST

Created attachment 207533 [details]
the profiler got this, when it was in dead lock state

Comment 7 kasper T

2011-11-25 08:52:12 EST

Created attachment 207534 [details]
anouther thread trace, when in dead lock, with more information

Comment 8 Paul Webster

2011-11-25 09:46:01 EST

What type of editors do you have open when this happens?

PW

Comment 9 Oleg Besedin

2011-11-25 13:44:58 EST

Are you by chance running out of memory, heap or PermGen?

Comment 10 kasper T

2011-11-26 06:59:31 EST

just plain text editor, the code editor, and the folder view (application/program folder). but run out of memory, i dont think so, since i have no problems in continue in typing, although i cannot copy, (ctrl+c fails for some reason, but ctrl+v does not ??), and if it was out of memory, would it not crash totaly / cause unpredicatble failuers ?, this is happening all the time, but eventually if i just "try" to ignore it enough, it sometimes dissapeare, for a few minutes or so. (if it is for any help, i have tried to clean my project options and change workspace, delete options files and such, without sucess).

Comment 11 Eclipse Genie

2019-08-30 13:01:19 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.