(In reply to Bryan Thrall [:bthrall] from comment #6) > I reproduced this in a local Firefox debug build on [mozilla-central rev. 792c98927914](https://hg.mozilla.org/mozilla-central/rev/792c98927914) and [analyzed it in Pernos.co](https://pernos.co/debug/kWiTqwvtrna-e6pMWeH0CA/index.html#f{m[A6PH,AapeAA_,t[AZY,B+Mt_,f{e[A6PH,Aahjgg_,s{acLVhoAAA,bAZo,uHPn+RA,oHQFgjg___/). All of the calls to [DebuggerScript::CallData::getPossibleBreakpoints()](https://searchfox.org/mozilla-central/source/js/src/debugger/Script.cpp#958) for the timer callback function return four unique breakpoint offsets. This indicates something is going wrong between there and where :bomsy was looking in comment 3. > > I also noticed that once multiple column breakpoints on line 21 are visible, you can add more by toggling the breakpoint on line 18 on and off. Reloading the page resets the number of column breakpoints on line 21 to two. > > I don't think the duplicate column breakpoints are coming from the SpiderMonkey Debugger API here, but if there's anything else you'd like me to look into, let me know! Thanks Bryan, for looking into this. I can confirm the issue was not the spider monkey api but rather a bug [here](https://searchfox.org/mozilla-central/rev/8ec3cc0472ad4f51b254728d024b696eaba82ba0/devtools/server/actors/source.js#333-337) when getting top level debuggee scripts. This issue was an descendant script was not getting removed because its parent script got removed first.
Bug 1874411 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Bryan Thrall [:bthrall] from comment #6) > I reproduced this in a local Firefox debug build on [mozilla-central rev. 792c98927914](https://hg.mozilla.org/mozilla-central/rev/792c98927914) and [analyzed it in Pernos.co](https://pernos.co/debug/kWiTqwvtrna-e6pMWeH0CA/index.html#f{m[A6PH,AapeAA_,t[AZY,B+Mt_,f{e[A6PH,Aahjgg_,s{acLVhoAAA,bAZo,uHPn+RA,oHQFgjg___/). All of the calls to [DebuggerScript::CallData::getPossibleBreakpoints()](https://searchfox.org/mozilla-central/source/js/src/debugger/Script.cpp#958) for the timer callback function return four unique breakpoint offsets. This indicates something is going wrong between there and where :bomsy was looking in comment 3. > > I also noticed that once multiple column breakpoints on line 21 are visible, you can add more by toggling the breakpoint on line 18 on and off. Reloading the page resets the number of column breakpoints on line 21 to two. > > I don't think the duplicate column breakpoints are coming from the SpiderMonkey Debugger API here, but if there's anything else you'd like me to look into, let me know! Thanks Bryan, for looking into this. I can indeed confirm the issue was not the spider monkey api but rather a bug [here](https://searchfox.org/mozilla-central/rev/8ec3cc0472ad4f51b254728d024b696eaba82ba0/devtools/server/actors/source.js#333-337) when getting top level debuggee scripts. This issue was an descendant script was not getting removed because its parent script got removed first.
(In reply to Bryan Thrall [:bthrall] from comment #6) > I reproduced this in a local Firefox debug build on [mozilla-central rev. 792c98927914](https://hg.mozilla.org/mozilla-central/rev/792c98927914) and [analyzed it in Pernos.co](https://pernos.co/debug/kWiTqwvtrna-e6pMWeH0CA/index.html#f{m[A6PH,AapeAA_,t[AZY,B+Mt_,f{e[A6PH,Aahjgg_,s{acLVhoAAA,bAZo,uHPn+RA,oHQFgjg___/). All of the calls to [DebuggerScript::CallData::getPossibleBreakpoints()](https://searchfox.org/mozilla-central/source/js/src/debugger/Script.cpp#958) for the timer callback function return four unique breakpoint offsets. This indicates something is going wrong between there and where :bomsy was looking in comment 3. > > I also noticed that once multiple column breakpoints on line 21 are visible, you can add more by toggling the breakpoint on line 18 on and off. Reloading the page resets the number of column breakpoints on line 21 to two. > > I don't think the duplicate column breakpoints are coming from the SpiderMonkey Debugger API here, but if there's anything else you'd like me to look into, let me know! Thanks Bryan, for looking into this. I can indeed confirm the issue was not the spider monkey api but rather a bug [here](https://searchfox.org/mozilla-central/rev/8ec3cc0472ad4f51b254728d024b696eaba82ba0/devtools/server/actors/source.js#333-337) when getting top level debuggee scripts. This issue was a descendant script was not getting removed because its parent script got removed first.