Running a command-line app with an error over and over does not stop the original program

[sethladd]

The automatic breakpoints in the error are cool, but the debugger doesn't stop when the program is run again.

Take any code that generates an error that the debugger will catch. Now run it again with Control-R. Notice how two instances of the program are running. I would have thought the original instance would have been shut down if I run it again.

I'm concerned that it's not obvious that multiple copies are running and eating away at system resources.

This is using editor Version 0.1.0.201207091114, Build 9474

[devoncarew]

I talked this over a bit w/ Keerti. I think our preferred solution is to allow two copies of the same application to be running, but not two copies of the same launch configuration. This will allow people who need do need two copies of an app running a way to accomplish that.

---

Set owner to @devoncarew.
Added this to the M1 milestone.
Added Accepted label.

[danrubel]

Removed this from the M1 milestone.
Added this to the Later milestone.

[sethladd]

I feel strongly this is an M1 feature. This is a poor user experience. If you're debugging an app, you can end up with numerous running (paused and failed) instances of your app, and the debug window becomes hard to navigate.

Devon and Keerti's proposed solution works for me, do not allow two command-line apps with the same launch config to run concurrently, especially if one of them failed.

---

Removed this from the Later milestone.
Added this to the M1 milestone.

[devoncarew]

Added Fixed label.