Can't capture after process as died

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Start Sawbuck
2. Enable Capture
3. Kill Sawbuck's process
4. Start Sawbuck again
5. Try to enable Capture

What is the expected output? What do you see instead?
Should enable Capture but it can't

I'm guessing we need to add an internal way to close previous Event Tracing 
Sessions if they were left open. Currently, we can use the logman -ets stop 
command manually, but it would be nice if Sawbuck would do it automagically.

Original issue reported on code.google.com by mad@chromium.org on 23 Dec 2009 at 9:01

GoogleCodeExporter commented 8 years ago

Original comment by si...@google.com on 25 Mar 2010 at 7:17

Changed state: Started

GoogleCodeExporter commented 8 years ago

Original comment by si...@google.com on 28 Mar 2010 at 10:02

Changed state: Fixed

google / sawbuck

Can't capture after process as died #1