Is there something special you need to

Is there something special you need to do to get local Chrome DevTools profiling working properly? I'm trying the following (with wrangler 3.22.3): * wrangler dev -e test --port 8787 * push 'd' to open chrome devtools, which opens https://devtools.devprod.cloudflare.dev/js_app?theme=systemPreferred&ws=127.0.0.1%3A9229%2Fws&domain=(REDACTED)&debugger=true * Confirm source files appear under "Sources" tab * in devtools->Profiler, click start * send a request to the local port, confirm the request appears in the devtools network tab * stop profiling * All I see in the CPU profile is (program), without any detail on the actual function calls (see screenshot) * I get the same result if I try chrome://inspect` and then "Open dedicated DevTools for Node" (see 2nd screenshot)
No description
No description
2 Replies
niels7
niels7OP12mo ago
I see another user reported a similar issue a couple months ago, but didn't seem to get a response: https://discord.com/channels/595317990191398933/1024343493251973190/1178012833192087672
Adam
Adam12mo ago
We've seen this before when it's either a smaller worker or just a single request to the Worker. If it's a more complex Worker, try sending multiple requests while profiling.
Want results from more Discord servers?
Add your server