1172114 - After setting a breakpoint in WebIDE debugger & relaunching a Firefox OS app, WebIDE opens a new debugger instance, without my breakpoint

Status: RESOLVED INVALID

(DevTools Graveyard :: WebIDE, defect)

Description

[Daniel Holbert [:dholbert]]

Let's say you want to debug an issue that occurs during the startup of a Firefox OS app.

STR:
 1. Start WebIDE with Firefox OS 3.0 simulator.
 2. Choose "Music" app from the app-chooser menu in WebIDE
 3. Launch music app in the Simulator window.
 4. Set a breakpoint somewhere, e.g. in music.js "init" function.
 5. Now let's re-start the music app. Long-click home-button on the Simulator window, and swipe the Music app off-screen, and then click on the music app on the homescreen.

ACTUAL RESULTS:
WebIDE now opens a *second debugger instance* (splitting vertically), with no breakpoints set in the new instance. The original instance, where I set my breakpoint, seems to be orphaned

EXPECTED RESULTS:
Same debugger instance should be used; my breakpoints should be honored at startup of the new app instance.


(I hit this with both simulator & a real device, and it's blocking me from figuring out what's going wrong in a bug during the startup of the music app in bug 1171202. :-/)

Comment 1

[Jeff Griffiths (:canuckistani) (:⚡︎)]

As a workaround, does using the debugger statement work?

Comment 2

[Daniel Holbert [:dholbert]]

I don't know what "using the debugger statement" means. Maybe you can try locally, using Firefox OS Simulator given the STR in comment 0?

(I haven't used WebIDE or the JS debugger much at all before. I was asked to try to get a backtrace of a particular Firefox OS issue I was hitting, and I tried & failed per comment 0.)

Comment 3

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Hmm, certainly the second toolbox instance should not appear...  Something may have changed recently, as I'm pretty sure that used to work.

In any case, I think you may be able to hit it by "reloading" within WebIDE:

1. Connect a toolbox to the app as before
2. Set your breakpoint
3. Click the reload icon in the top bar, or press Cmd-R

Or, you can try Jeff's idea, which involves editing the source to add "debugger;" where the breakpoint should go.  If the toolbox is open, it should break on any such lines.

Comment 4

[Daniel Holbert [:dholbert]]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #3)
> 2. Set your breakpoint
> 3. Click the reload icon in the top bar, or press Cmd-R

Ah! Thanks, that does indeed work -- I do see the breakpoint being triggered during startup when I reload. So, that's a workaround (and probably the best-practices) for performing the action I was trying to do in step 0.

Anyway; leaving this bug open, since it seems the ACTUAL RESULTS from comment 0's STR (ending up with multiple debugger instances) are still incorrect.

Comment 5

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Apps are being removed with B2G cleanup.