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

Bug 75458

Summary:	[Progress] Improper use of Progress service API results in lockup on Mac
Product:	[Eclipse Project] Platform	Reporter:	Michael Valenta <Michael.Valenta>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Michael Valenta

2004-10-01 10:58:50 EDT

We use the PlatformUI.getWorkbench().getProgressService().run() API to perform 
work in a progress dialog. Inside out runnable, we prompt for user input. On 
the Mac, this will result in a freeze since the proper dialog parenting is not 
done. Since there is no way to get the proper parenting with this API, it 
should have a comment in the javdoc stating that prompting using a dialog 
should not be done from within the runnable as this will reuslt in improper 
behavior on some platforms and deadlock on others. The improper behavior is on 
windows where the dialog is opened but appears in the wrong place.

Comment 1 Tod Creasey

2004-10-01 13:14:12 EDT

I have made this explicit in the Dialog and runInUI API in build >20041001

Comment 2 Michael Valenta

2004-10-06 09:49:46 EDT

Actually, the method I was using was run and not runInUI. I guess this makes 
it complicated since it's an inherited method but there really needs to be a 
strong statement that prompting within any of the methods run, runInUI and 
busyCursorWhile can cause deadlock. Instead of saying "modal dialogs should be 
avoided" I would rather see wording like "prompting within the runnable of 
this method can cause deadlock on some platforms. If you need to prompt within 
your runnable, do the following..."

Comment 3 Susan McCourt

2009-07-09 19:30:30 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 4 Eclipse Webmaster

2019-09-06 15:33:01 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.

Comment 5 Eclipse Genie

2021-11-19 03:10:07 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.