Mac: Brackets won't quit in subsequent sessions after using Dev Tools

[couzteau]

1. Run brackets
2. open test runner chrome debug tools
3. quit brackets
4. restart brackets.
5. Now brackets won’t quit unless I run quit from the OSX dock.

results:
At step 3 I'd expect my chrome dev tools to close. But they stay open
At step 5 I'd expect brackets to quit via CMD-Q or via Quit from menu

Env OSX 10.7, 10.8, 10.9

---

Slightly simplified steps:

1. Run Brackets
2. Debug > Show Developer Tools
3. Close Brackets
4. Do not close Chrome
5. Restart Brackets
6. Cmd-Q

Results:
Bracket won't quit

[jasonsanjose]

I'm seeing this too on 10.7. But in step 2 I don't open the unit test window, I just go straight to Debug > Show Developer Tools.

[JeffryBooher]

@jasonsanjose are you running OSX 10.9 as well? Just wondering if it's something new with 10.9

[JeffryBooher]

N/M @jasonsanjose -- I see you e-mail now that you see it on 10.7

[jasonsanjose]

@redmunds would this closed PR fix this? adobe/brackets-shell#374

[redmunds]

@fungl164 Can you take a look at this one? I'm wondering if it has something to do with your recent Chrome changes.

[redmunds]

@jasonsanjose I was just trying that. I'm not sure why, but Dev Tools still open in Chrome live-dev profile with that branch (randy/dev-tools-no-debug-connection), so problem is not fixed.

[redmunds]

Doh! I forgot to rebuild. That branch does fix it if Chrome is not running, but Dev Tools fail to launch if Chrome is already running. I'll play around with it.

[peterflynn]

Updated title to clarify that this only occurs in dev tools related workflows.

[redmunds]

I can also hit problem with this scenario:

1. Open Brackets
2. Start Live Dev
3. In Chrome window with Live Dev (i.e. live-dev profile), open a new Tab
4. In new Tab, go to localhost:9234 and click on the Dev Tools link
5. Close and restart Brackets

So, opening Dev Tools in Chrome with default profile may not be enough to fix this problem because you can manually open Dev Tools in Chrome window with live-dev profile.

[redmunds]

Note that this only happens on Mac.

When I try to reproduce on Windows, when Brackets is shutdown, I see a message in Chrome Dev Tools window: "Detached from Target. Remote Debugging has been terminated with reason target_closed. Please re-attach to new target".

I don't see that message in Chrome window on Mac.

[fungl164]

@redmunds et al. I'm on #brackets irc if you want to chat...

[fungl164]

Based on the symptoms and behavior, I believe the problem is most likely that the native app is for some reason not closing the main window. I'm not sure if this is the proper place to force quit the app on exit, but if seems to fix the problem. see (https://github.com/fungl164/brackets-shell/tree/devtools-close)

[fungl164]

@redmunds this should work without any changes to the current master (e.g. no gist edits)

[redmunds]

@fungl164 Thanks for continuing to look at this. The problem is definitely that Brackets is not properly terminating.

Unfortunately your suggestion won't work in the case where there are unsaved documents at shutdown. Instead of prompting user to save documents, it shuts down immediately so unsaved changes are lost.

[fungl164]

@redmunds is there some code already available that can be called to ensure files are saved (either in the appshell or in brackets)?