Bug 560857 - UI freezing when Open Implementations
Summary: UI freezing when Open Implementations
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.15   Edit
Hardware: PC Windows 10
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-06 08:32 EST by Dennis CLA
Modified: 2024-02-20 18:59 EST (History)
3 users (show)

See Also:


Attachments
strack trace (52.74 KB, text/plain)
2020-03-06 08:32 EST, Dennis CLA
no flags Details
stack trace2 (66.25 KB, application/octet-stream)
2020-03-06 08:33 EST, Dennis CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis CLA 2020-03-06 08:32:52 EST
Created attachment 282032 [details]
strack trace

My Eclipse freeze quite often when I doing "Open Implementations" from Ctrl+Click menu in editor.

It happens when you have a number of projects opens and many JARs in theirs class-path.

But I think it is a general UI framework design format that it block and wait for information.

Regardless of what can be popup underneath, they should come stream async progressively. Not block and wait for result.
Comment 1 Dennis CLA 2020-03-06 08:33:32 EST
Created attachment 282033 [details]
stack trace2
Comment 2 Eclipse Genie CLA 2022-02-25 17:19:38 EST
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.
Comment 3 Eclipse Genie CLA 2024-02-20 18:59:31 EST
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.