Concurrent debugging of multiple addons
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
People
(Reporter: czerny.jakub, Assigned: jimb)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Reporter | ||
Updated•10 years ago
|
Updated•6 years ago
|
Comment 1•5 years ago
|
||
I can open two separate toolboxes for two addons, so I am not able to reproduce the original problem.
But, I am seeing an issue with concurrent stepping
STR:
- Clone this addon: https://github.com/firefox-devtools/har-export-trigger Clone it twice on your machine and change the ID in the manifest.json file, so you have two different addons
- Use
about:debugging#/runtime/this-firefox
to load both of them as separate addons - Click the
Inspect
button for both these addons to open two separate toolboxes (I am moving them into two separate browser windows, so it's easier to follow what's happening) - Select Debugger panel and create BP in
devtools.js
file inonMessage
function - again for both of them - Load this page:
http://janodvarko.cz/test/harexporttrigger/
open content DevTools Toolbox on it and click ongetHar
button (at the bottom of the page) - Both breakpoints created in step #4 should hit
- I can step in the first addon toolbox just fine (try just once, so the execution is still stopped), but stepping over in the second toolbox doesn't work properly. After first step over, the execution/debug line disappears. But the debugger is still in paused mode
Note that after resuming both and clicking on getHar
buttton again the breakpoint in the first addon toolbox doesn't hit at all.
If I resume the first toolbox the stepping works fine in the second toolbox.
Could this be related to run-to-completion?
Honza
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Honza, I tried this out, but I couldn't find the devtools.js source file in the debugger. Is there something I'm missing?
Assignee | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
The devtools.js
file comes from the extension, see the attached screenshot.
I can still reproduce the problem on my machine.
Honza
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
(Lovely. I can bugzilla.)
Assignee | ||
Comment 7•5 years ago
|
||
In any case, we have something interesting to look into here.
Assignee | ||
Updated•5 years ago
|
Comment hidden (off-topic) |
Comment 9•2 years ago
|
||
Sorry, there was a problem with the detection of inactive users. I'm reverting the change.
Updated•2 years ago
|
Description
•