Steps to reproduce: - Connect App Manager to device - Debug an app - Unplug/replug the cable - Connect to device again - Try to debug the same app Observed: - No side tab is opened for the app, no toolbox is shown, the background is grey - Debugging other apps works Expected: - Debugging the same app again after disconnect should work

The app actor front caches targets when you connect to an app. It uses the target's close event to remove the target from its cache. However, the target close event was not being triggered if the client is closed out from under the target, so now the target watches for this. Try: https://tbpl.mozilla.org/?tree=Try&rev=3575fc05f978

Comment on attachment 8381921 [details] [diff] [review] Close target when client is closed Review of attachment 8381921 [details] [diff] [review]: ----------------------------------------------------------------- Good catch! ::: browser/devtools/framework/target.js @@ +385,5 @@ > /** > * Teardown listeners for remote debugging. > */ > _teardownRemoteListeners: function TabTarget__teardownRemoteListeners() { > + this.client.removeListener("closed", this.destroy); You could have used addOneTimeListener and avoided this if you wanted.

Comment on attachment 8381921 [details] [diff] [review] Close target when client is closed [Approval Request Comment] Bug caused by (feature/regressing bug #): bug 918695 User impact if declined: App Manager broken when attempting to re-debug an app after getting disconnected, requires restarting Firefox to fix Testing completed (on m-c, etc.): m-c Risk to taking this patch (and alternatives if risky): Low String or IDL/UUID changes made by this patch: None

Hmm, never mind, seems only Firefox 30 is affected. Regression must have been triggered by some other change then.

Reproduced using Firefox OS 1.2 simulator. Verified fixed on latest Aurora 20140423004003.