Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SourceActorProxy Error on Setting Breakpoints

Open
#302 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
angular, typescript, vscode, webpack
Domain
devtools, frontend

Research direction

Reproduce the breakpoint failure using the posted launch.json configuration against the Angular application, then start with the SourceMappingSourceActorProxy and SourceActorProxy log entries around getBreakpointPositionsCompressed. Done means setting a breakpoint from VS Code no longer produces the noSuchActor error and the breakpoint can be hit.

Written by the indexing model from the issue text.

Description

Hello, I'm having a repeat problem lately when trying to use this extension to debug an Angular 14 application in VSCode.

My OS is macOS 12.5.1 (x86_64)
Browser is Firefox Developer Edition 105.0b2
VSCode Version is 1.70.2
Extension Version is 2.9.8
Angular Version 14.0.5

I find that any time I set a breakpoint in a file while I have Firefox debugging started, I receive something to the effect of:

DEBUG|044.875|BreakpointsManager: Setting 1 breakpoints for /path/to/src/app/app.component.ts
DEBUG|044.876|SourceAdapter: Going to delete 0 breakpoints
DEBUG|044.876|SourceAdapter: Going to add 1 breakpoints
DEBUG|044.888|SourceMappingSourceActorProxy: Calculating ranges for webpack:///src/app/app.component.ts within its generated source
DEBUG|049.077|SourceMappingSourceActorProxy: Fetching generated breakpoint locations for webpack:///src/app/app.component.ts, 928:0 - 1131:0
DEBUG|049.077|SourceActorProxy: Fetching breakpoint positions of http://localhost:4200/main.js for range: {"start":{"line":928,"column":0},"end":{"line":1131,"column":0}}
DEBUG|049.077|DebugConnection: Sending request {"to":"server1.conn0.child10/source26","type":"getBreakpointPositionsCompressed","query":{"start":{"line":928,"column":0},"end":{"line":1131,"column":0}}}
DEBUG|049.078|DebugConnection: Received response/event {"from":"server1.conn0.child10/source26","error":"noSuchActor","message":"No such actor for ID: server1.conn0.child10/source26"}
ERROR|049.079|SourceActorProxy: No such actor "server1.conn0.child10/source26"

My launch.json config is:

{
    "name": "Build then Launch Firefox",
    "request": "launch",
    "type": "firefox",
    "url": "http://localhost:4200/",
    "webRoot": "${workspaceFolder}",
    "preLaunchTask": "npm: starthot",
    "log": {
        "fileName": "${workspaceFolder}/vscode-firefox-debug.log",
        "fileLevel": {
            "default": "Debug"
        }
    }
}

where npm: starthot is simply a wrapper for ng serve with the specific configuration we use for debugging supplied.

It seems the error is that the server1.conn0.child10/source26 actor does not exist. I've verified that the various under-the-hood settings in about:config are matching and we're using the default debugging ports. I can confirm that launch does start Firefox in remote control mode evidenced by the red-striped URL with a little robot, and if I open the devtools in the browser itself, I can navigate to the Webpack sources in the current thread, set breakpoints, and they are even hit in the browser console, but the breakpointing connection between VSCode/the extension and the browser seems to be getting stuck.

Any ideas or suggestions? Let me know if any further info is needed. Thank you!

Dominant language
TypeScript
Stars
447
Forks
76
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firefox-devtools/vscode-firefox-debug

All issues in firefox-devtools/vscode-firefox-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.