Bug 204813 - [quick fix] UI freezes during "Rename Compilation Unit" Quick Fix while building workspace
Summary: [quick fix] UI freezes during "Rename Compilation Unit" Quick Fix while build...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 187351
Blocks:
  Show dependency tree
 
Reported: 2007-09-27 10:30 EDT by Michael Schneider CLA
Modified: 2022-07-31 04:50 EDT (History)
2 users (show)

See Also:


Attachments
trace (26.28 KB, application/octet-stream)
2007-09-27 10:30 EDT, Michael Schneider CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schneider CLA 2007-09-27 10:30:21 EDT
Created attachment 79287 [details]
trace

Build ID: 20070626-0630

Steps To Reproduce:
1. Open a workspace that takes some time to rebuild
2. clean and rebuild all
3. while rebuilding, open a class, locally rename it, and apply the "Rename Compilation Unit" quickfix

Observe: The UI freezes until building the workspace completed.

See attached trace for more informations
Comment 1 Martin Aeschlimann CLA 2007-09-28 10:53:04 EDT
will be fixed when we solve bug 187351
Comment 2 Eclipse Genie CLA 2020-06-23 15:46:00 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.
Comment 3 Eclipse Genie CLA 2022-07-31 04:50:28 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.