Open Bug 1075185 Opened 10 years ago Updated 2 years ago

Concurrent debugging of multiple addons

Categories

(DevTools :: Debugger, defect, P3)

32 Branch
x86_64
Linux
defect

Tracking

(Not tracked)

People

(Reporter: czerny.jakub, Assigned: jimb)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Build ID: 20140831201947 Steps to reproduce: 1. Make sure the you have at least two debug-able addon installed 2. Make sure you have addon debugging allowed (settings of Developer tools) 3. Open about:addons 4. Click 'Debug' on arbitrary addon, confirm in following dialog 5. Click 'Debug' on different addon Actual results: Nothing visible to regular user. Browser console (shell) output: DBG-SERVER: Could not start debugging listener on '6080': [Exception... "Component returned failure code: 0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]" nsresult: "0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE)" location: "JS frame :: resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js :: DS_openListener :: line 463" data: no] Expected results: Either a new debugger should be open or user should be notified that such action (concurrent debugging) is not possible.
Component: Untriaged → Developer Tools
Product: Firefox → DevTools

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:

  1. 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
  2. Use about:debugging#/runtime/this-firefox to load both of them as separate addons
  3. 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)
  4. Select Debugger panel and create BP in devtools.js file in onMessage function - again for both of them
  5. Load this page: http://janodvarko.cz/test/harexporttrigger/ open content DevTools Toolbox on it and click on getHar button (at the bottom of the page)
  6. Both breakpoints created in step #4 should hit
  7. 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

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(jimb)
Priority: -- → P3
Component: General → Debugger

Honza, I tried this out, but I couldn't find the devtools.js source file in the debugger. Is there something I'm missing?

Flags: needinfo?(odvarko)
Flags: needinfo?(jimb)
Attached image image.png (deleted) —

The devtools.js file comes from the extension, see the attached screenshot.

I can still reproduce the problem on my machine.

Honza

Flags: needinfo?(odvarko)
Flags: needinfo?(jimb)
Attached image screen shot (deleted) —
Flags: needinfo?(jimb)
Comment on attachment 9107318 [details] screen shot Here's what I see... there is no devtools.js source file.
Attachment #9107318 - Attachment description: Here's what I see... there is no devtools.js source file. → screen shot

(Lovely. I can bugzilla.)

In any case, we have something interesting to look into here.

Assignee: nobody → jimb

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Assignee: nobody → jimb
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: