ejego
ejego
PostsComments
CDCloudflare Developers
Created by ejego on 7/30/2024 in #workers-help
VS Code debugger stuck on first breakpoint
Hey 👋 I've been using the VS Code debugger for a few days to debug my Workers project, and it worked perfectly. But for some reason it stopped working since yesterday. The debugger hits the 1st breakpoint, and it got stuck: I can't see variables values or anything, and I can't even continue the debug session after that, the debugger crashes in some way. Also, the code is executed even if the debugger hits the breakpoint. In my terminal and in the debug logs I have the following message, that I believe might show the source of the problem: 
workerd/jsg/util.c++:276: error: e = kj/compat/http.c++:5755: failed: WebSocket protocol error; protocolError.statusCode = 1009; protocolError.description = Message is too large: 1050585 > 1048576
workerd/jsg/util.c++:276: error: e = kj/compat/http.c++:5755: failed: WebSocket protocol error; protocolError.statusCode = 1009; protocolError.description = Message is too large: 1050585 > 1048576
I don't know why a WebSocket message would be that size, my app ins't doing crazy stuff, it is quite new. It is just bound to D1, R2 and KV instances. Anyway, does anybody had this issue or know how I can fix this? By reducing the WebSocket messages size somehow or increasing the messages size limit may be? Here is my VS Code debug configuration if that may help: 
{
  "name": "Wrangler",
  "type": "node",
  "request": "attach",
  "port": 9229,
  "cwd": "/",
  "resolveSourceMapLocations": [
    "!node_modules/@prisma/**"
  ],
  "attachExistingChildren": false,
  "autoAttachChildProcesses": false,
  "sourceMaps": true
}
{
  "name": "Wrangler",
  "type": "node",
  "request": "attach",
  "port": 9229,
  "cwd": "/",
  "resolveSourceMapLocations": [
    "!node_modules/@prisma/**"
  ],
  "attachExistingChildren": false,
  "autoAttachChildProcesses": false,
  "sourceMaps": true
}
Also, my code runs in WSL (Windows Subsystem for Linux). Thanks! 🙂
2 replies