Bug 294091 - [Undo] Deleting a large set of projects causes Eclipse to freeze while creating "workspace undoable operation"
Summary: [Undo] Deleting a large set of projects causes Eclipse to freeze while creati...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-03 12:18 EST by Pawan Singh CLA
Modified: 2019-09-06 16:05 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pawan Singh CLA 2009-11-03 12:18:37 EST 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15
Build Identifier: 

I have 284 projects in my workspace. I want to remove all of them. So I select all and delete. I do not delete them from disk - but simply remove them from my workspace. This used to work beautifully with Eclipse 3.3. But in Eclipse 3.4, it wants to create a "Workspace undoable operation". You see a dialog popup which sits there for 30-40 minutes creating this undoable operation. I do not want to undo this!!! Why is this operation not cancellable?

Reproducible: Always

Steps to Reproduce:
See above
Comment 1 Pawan Singh CLA 2009-11-03 14:12:56 EST 
Another complication here is that it seems like build is also starting in the background and that will use up extra CPU cycles unncessarily as well.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:05:22 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.