Skip to content

Breakpoints for worker bind after the worker has already started #1719

Closed
@rchiodo

Description

Describe the bug
If your worker map file is too large, breakpoints won't bind until after the worker is already running

To Reproduce
The only steps I have to reproduce is to use our real product. I'm running a worker thread that contains our entire language server and the breakpoints for the worker thread bind on a time delay after the worker has actually started.

Meaning I can't debug startup of the worker thread.

The breakpoints do bind later, and I can debug messages sent to the server (as I can stick a breakpoint in the client).

Log File

vscode-debugadapter-d1089d59.json.gz

VS Code Version: 1.79.0-insiders

Additional context
Add any other context about the problem here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

author-verification-requestedIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions