Community
Participate
Working Groups
Created attachment 90513 [details] screen capture - frozen progress bar Build ID: 3.2.2 Steps To Reproduce: 1. Start "an IBM product based on Eclipse" - ask me for details. 2. Start WPS server 3. Open Admin Console (from Servers View) and log in 4. Click "log off" link and close the Admin Console window right away. Defect Description: Loggin Off causes the progress bar to appear on the status bar. The progress bar stops progressing (and stays on the status bar - looks like frozen) if I close the Admin Console window before the progress bar reaches 100%. More information: This same happens during initialization or loggin in to the Admin Console, logging in/off and using BPCE etc. (ask me for details).
Can you provided a test case that doesn't rely on any IBM properties?
I do not think I can.
This is because someone is using the IStatusLineManager show progress. My guess is that the Admin console window is not clearing the progress when it is closed that way. Look at senders of getProgressMonitor in this code.
Should the Admin Console window clear the progress when it's closed / terminated or this is Eclipse's task to detect that this window was closed?
If your monitor never calls done() the status line doesn't know that it needs to be closed.
I've been talking to Admin Console developers - this is a web application displayed inside Eclipse in a "browser widget". Probably it is an issue with "browser widget". What component could it be? SWT? Please help me finding the right component.
User Assistance most likely if it is an issue with how the browser support interact with the workbench
Do you have a reference to a bug sent to user assistance about the browser issue?
"any reference" - do you mean "any response"? No, nobody contacted me...
In comment 6 you mention >'ve been talking to Admin Console developers - this is a web application displayed inside Eclipse in a "browser widget". Probably it is an issue with "browser widget". What component could it be? SWT? Please help me finding the right component. I mentioned it was UA. Did you follow up? BTW SWT does supply the widget so it could be then too.
I thought you've changed the component. I'm setting it now to SWT. Is that enough?
They will need more details than what you have here to reproduce this.
(In reply to comment #12) > They will need more details than what you have here to reproduce this. Timed out, closing report. If this problem still happens for you with the recent Eclipse 4.3 release, and you can provide a means of reproducing it on this end (eg.- an Eclipse plug-in) then please reopen with the additional info, thanks.