Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321096 - Launching external tool (command prompt) causes the progress bar to get stuck at 57%
Summary: Launching external tool (command prompt) causes the progress bar to get stuck...
Status: CLOSED DUPLICATE of bug 323953
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-28 04:16 EDT by Patrik Andrén CLA
Modified: 2010-08-30 16:29 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrik Andrén CLA 2010-07-28 04:16:33 EDT
Build Identifier: 20100617-1415

When launching a command prompt - either a plain one, or a prompt with some commands in, the progress bar does not stop. It get stuck at 57% and keep "painting" the blue icons in the screen. Everything works fine tough - it launches what it's suppose to launch but the bars does not stop.

It's very annoying to have a moving blue bar in the corner of the screen taking the focus out of what you are supposed to do.

I realize that this bug is a minor one even though it's severe for me since I cannot stand to see that moving thing in the corner of the screen. It seems to be an easy fix?

Reproducible: Always

Steps to Reproduce:
1. Create an external tool configuration to C:\WINNT\system32\cmd.exe
2. Run it
3. See it starts, and work - but the progress bar get stuck at 57% with it moving blue icons.
Comment 1 Josh Davidson CLA 2010-07-29 10:56:53 EDT
I have the exact same issue, and I agree it's annoying.  I've also experienced an issue where if left up long enough, Eclipse pegs the cpu and is unable to terminate the external tool.
Comment 2 Darin Wright CLA 2010-08-30 16:29:44 EDT
This is a dup of bug 323953.

*** This bug has been marked as a duplicate of bug 323953 ***