You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[User-reported issue] DevTools panels are blank in VS Code #5659
Based on details shared, I think this is more likely an issue with the extension than DevTools. Feel free to send this back if we need to do more investigation on the DevTools side. Thanks!
When I toggle dev tools it opens an external window with the chromium tools.
The console contains the following.
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-vsliveshare.vsliveshare' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.gather' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.vscode-pylance' wants API proposal 'mcpConfigurationProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:440 INFO Started local extension host with pid 952150.
workbench.html:1 [GroupMarkerNotSet(crbug.com/242999)!:A0F02700BC150000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader (about:flags#enable-unsafe-swiftshader) flag to opt in to lower security guarantees for trusted content.
workbench.html:1 [.WebGL-0x3dc01bd3800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
workbench.html:1 [.WebGL-0x3dc01bd3800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
workbench.html:1 [.WebGL-0x3dc01bd3800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.dart.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/dart/syntaxes/dart.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/dart-code.dart-code-3.116.0/syntaxes/dart.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/mtxr.sqltools-0.28.4/language/sql.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.java.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/java/syntaxes/java.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/redhat.java-1.44.0-linux-x64/language-support/java/java.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.groovy.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/groovy/syntaxes/groovy.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/vscjava.vscode-gradle-3.16.4/syntaxes/groovy.tmLanguage.json
register @ TMScopeRegistry.ts:46
workbench.html:1 [.WebGL-0x3dc01bd3800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels (this message will no longer repeat)
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.dart.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/dart/syntaxes/dart.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/dart-code.dart-code-3.116.0/syntaxes/dart.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/mtxr.sqltools-0.28.4/language/sql.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.java.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/java/syntaxes/java.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/redhat.java-1.44.0-linux-x64/language-support/java/java.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.groovy.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/groovy/syntaxes/groovy.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/vscjava.vscode-gradle-3.16.4/syntaxes/groovy.tmLanguage.json
register @ TMScopeRegistry.ts:46
console.ts:137 [Extension Host] extension "spaces-inside-braces" is now active
console.ts:137 [Extension Host] Activating DeepCodeExtension
console.ts:137 [Extension Host] DeepCode context advanced false
console.ts:137 [Extension Host] DeepCode context deprecated true
log.ts:440 INFO Settings Sync: Account status changed from uninitialized to available
console.ts:137 [Extension Host] Checking whether to register object drop extension
console.ts:137 [Extension Host] Registering object drop provider
console.ts:137 [Extension Host] Registered object drop provider
marketplace.visualstudio.com/_apis/public/gallery/vscode/deepcode/deepcode/latest:1 Failed to load resource: the server responded with a status of 404 ()
marketplace.visualstudio.com/_apis/public/gallery/vscode/jozsefsallai/curlybrace/latest:1 Failed to load resource: the server responded with a status of 404 ()
marketplace.visualstudio.com/_apis/public/gallery/vscode/fabianlauer/vs-code-xml-format/latest:1 Failed to load resource: the server responded with a status of 404 ()
log.ts:440 INFO [perf] Render performance baseline is 22ms
console.ts:137 [Extension Host] rejected promise not handled within 1 second: CodeExpectedError: Unable to write to User Settings because print.browser.useAlternate is not a registered configuration.
Ims @ console.ts:137
console.ts:137 [Extension Host] stack trace: CodeExpectedError: Unable to write to User Settings because print.browser.useAlternate is not a registered configuration.
at e1t.z (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:6793)
at e1t.F (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:9281)
at e1t.o (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:3874)
at Object.factory (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:3774)
at Nv.j (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:30:75710)
at vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:30:75622
at new Promise (<anonymous>)
at Nv.queue (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:30:75564)
at e1t.writeConfiguration (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:3743)
at uhn.Hb (vscode-file://vscode-app/snap/code/203/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:3605:42740)
Ims @ console.ts:137
log.ts:460 ERR Unable to write to User Settings because print.browser.useAlternate is not a registered configuration.
error @ log.ts:460
I went on an disabled all extensions except for dart and flutter the console now shows (after selecting the toggle option).
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-vsliveshare.vsliveshare' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.gather' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:450 WARN Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.vscode-pylance' wants API proposal 'mcpConfigurationProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
warn @ log.ts:450
log.ts:440 INFO Started local extension host with pid 957007.
workbench.html:1 [GroupMarkerNotSet(crbug.com/242999)!:A0F02700B4350000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader (about:flags#enable-unsafe-swiftshader) flag to opt in to lower security guarantees for trusted content.
workbench.html:1 [.WebGL-0x1184032eb100]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
workbench.html:1 [.WebGL-0x1184032eb100]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
workbench.html:1 [.WebGL-0x1184032eb100]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.dart.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/dart/syntaxes/dart.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/dart-code.dart-code-3.116.0/syntaxes/dart.json
register @ TMScopeRegistry.ts:46
workbench.html:1 [.WebGL-0x1184032eb100]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels (this message will no longer repeat)
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.dart.
Old grammar file: file:///snap/code/203/usr/share/code/resources/app/extensions/dart/syntaxes/dart.tmLanguage.json.
New grammar file: file:///home/bsutton/.vscode/extensions/dart-code.dart-code-3.116.0/syntaxes/dart.json
register @ TMScopeRegistry.ts:46
log.ts:440 INFO Settings Sync: Account status changed from uninitialized to available
log.ts:440 INFO [perf] Render performance baseline is 21ms
webviewElement.ts:487 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:487
webviewElement.ts:487 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:487
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-zwO5m8djEu7lQSKWEk91IY5DFORrHkGqNb3Yg15UFwM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
index.html?id=1849f7cb-c4da-486f-8d83-88f515ea0536&parentId=1&origin=c2c1f0b9-913f-42b3-999c-9253c5a92918&swVersion=4&extensionId=&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&disableServiceWorker=true:1062 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-eeaStw0+rBcPJr0ruw2BfYSqbxjqh+AI0p15sauxhjk='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
(anonymous) @ index.html?id=1849f7cb-c4da-486f-8d83-88f515ea0536&parentId=1&origin=c2c1f0b9-913f-42b3-999c-9253c5a92918&swVersion=4&extensionId=&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&disableServiceWorker=true:1062
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'". Either the 'unsafe-inline' keyword, a hash ('sha256-HvPELhsDYalo30VxCTF6xR1X4dJg2hYtJRYP8LH98C4='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Odd - I haven't been able to repro yet. The text in the error ("style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'") doesn't seem like one of our headers because the only style-src we have is style-src 'unsafe-inline'.
I found a similar issue in the VS Code repro from a long time ago (microsoft/vscode#86399) but it seemed Edge-specific and seemed to go away.
whether this is just standard VS Code desktop (and not something like the web version)
if you clear the VS Code dev tools console prior to trying to open it, and then open it, what the output is? (I'm trying to determine if any of the output you provided above is from prior to opening and me be unrelated)
Searching for some parts of that also led me to microsoft/vscode#249995 which although not exactly the same (it says blocked, not a CSP error), seems similar.
@bsutton could you also try opening a Markdown file and running the Markdown: Open preview command to see whether that works (I think it uses a webview in a similar way to us, so if that fails it might narrow it down to VS Code and give a simple repro to report there).
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.35.1, on Ubuntu 25.04 6.11.0-26-generic, locale en_AU.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2024.3.2)
[✓] VS Code (version 1.103.0)
[✓] Connected device (2 available)
[✓] Network resources
• No issues found!
@bsutton thanks for confirming. I still can't repro this, however the new E2E tests that use Playwright started failing a few days ago, and appear to be doing so consistently. The screenshot looks suspiciously like yours:
Interestingly, both you and that bot are on Linux, so I wonder if that might be related.
I've filed Dart-Code/E2E-Tests#4 for that issue and I'll see if I can figure out what changed around 3-4 days ago that made it go from 100% green to 100% red in case it might be the same here.
Only inconsistency is that I reported this 2 weeks ago against flutter dev tools but you are saying that the e2e only started failing 3-4 days ago.
Yeah, that's what makes me unsure. I was thinking maybe there could be something that the GitHub runner picked up later than your machine, however based on my debugging in that issue, it seems like it might be tied to a Flutter change which I think rules that out (I'll continue to try to bisect it to a single commit though).
I remember in the past we had some issue on Linux with a GPU driver, and wonder if this could be similar. I found the issue at #4855 but the error in the console is very different (and it at least made some attempt to render something, whereas for you it seems like it hasn't - although from the console it seems like the DevTools code is definitely running).
Friendly ping! I've not been able to repro this any more and suspect it may be fixed. Please let me know if you can still repro this. Otherwise, I'll let the bot close it after no replies for a while. Thanks!
This issue has been marked stale because it is tagged awaiting-info for 20 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days.
Adding data points to this issue — we did a deep elimination on Windows and it's still reproducible on current versions. Happy to provide more diagnostics.
Environment
Component
Version
OS
Windows 11 x64
VS Code
1.140.0 (07f806f999, 2026-09-30), user installer, GPU hardware acceleration active
The embedded DevTools pages (tried both sidebar and "beside" webviews, and the debug-toolbar button) stay blank/gray forever. No DevTools UI ever renders. The same DevTools build opened in a regular Chrome on the same machine (dart devtools + http://127.0.0.1:<port>/inspector?uri=...) loads and renders fine, and connects to the app.
What we ruled out
SDK side is healthy: dart devtools --machine starts, serves HTTP 200; DTD alive; vm.register succeeds in the DTD log.
Extension-side spawn is healthy: the devtools log shows server.started, and the DevTools server receives connections when pages are open.
Not the legacy version file issue (extension 3.145 reads bin/cache/flutter.version.json, which is valid).
Not the extension-update stale-webview-cache problem: cleared Code\Cache, CachedData, Code Cache, GPUCache, Service Worker, removed the obsolete 3.144.0 extension folders, rebooted the PC — panel is still blank.
Not HTTP proxy settings (a local proxy was configured; plain HTTP GET and full WebSocket handshakes to localhost were verified to pass, and Chromium implicit loopback bypass should also apply).
Launching VS Code with --disable-features=LocalNetworkAccess,PrivateNetworkAccessRespect does not change anything.
No third-party AV, no IFEO/WMI interceptors.
Observed in the main-window DevTools console when the panel opens
While the blank panel is open there are zero established TCP connections from the webview to the DevTools server — the iframe never starts fetching. Other extensions' webviews in the same window (which don't load http://127.0.0.1 resources cross-origin) render fine.
Question
Given Chrome 142+ Local Network Access enforcement for subframe navigation/fetches to 127.0.0.1 from a non-local origin (vscode-webview://), does the extension have plans to serve the embedded DevTools frame in a way that avoids cross-origin private-network requests (or any other workaround) for VS Code builds whose Chromium says Unrecognized feature: 'local-network-access' while still blocking? Right now the only working workaround is dart.devToolsLocation: external (browser), which loses the embedded experience.
@Arkh74278 the issue you're seeing is a bit different to what was reported here. You're hitting a new bug in VS Code - see #6209 and microsoft/vscode#339079.
It's fixed in the upcoming v1.141 of VS Code. See #6209 (comment) for the workarounds I know of.
Activity
bsutton commentedon Aug 20, 2025
If you need more diagnostic, I'm happy to help.
DanTup commentedon Aug 20, 2025
@bsutton if you click Help -> Toggle Developer Tools inside VS Code, can you are:
Thanks!
bsutton commentedon Aug 21, 2025
When I toggle dev tools it opens an external window with the chromium tools.
The console contains the following.
bsutton commentedon Aug 21, 2025
I went on an disabled all extensions except for dart and flutter the console now shows (after selecting the toggle option).
bsutton commentedon Aug 21, 2025
after disabling all extensions (except for dart and flutter) and restarting vs-code the flutter inspect still won't open inside vs-code.
DanTup commentedon Aug 26, 2025
Odd - I haven't been able to repro yet. The text in the error (
"style-src 'nonce-12a0e76d-b2a7-4ab3-b217-0ce9d79bc3e0'") doesn't seem like one of our headers because the onlystyle-srcwe have isstyle-src 'unsafe-inline'.I found a similar issue in the VS Code repro from a long time ago (microsoft/vscode#86399) but it seemed Edge-specific and seemed to go away.
@bsutton can you confirm:
There is a URL in the error that looks like this:
index.html?id=1849f7cb-c4da-486f-8d83-88f515ea0536&parentId=1&origin=c2c1f0b9-913f-42b3-999c-9253c5a92918&swVersion=4&extensionId=&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&disableServiceWorker=true:1062
Searching for some parts of that also led me to microsoft/vscode#249995 which although not exactly the same (it says blocked, not a CSP error), seems similar.
@bsutton could you also try opening a Markdown file and running the Markdown: Open preview command to see whether that works (I think it uses a webview in a similar way to us, so if that fails it might narrow it down to VS Code and give a simple repro to report there).
bsutton commentedon Aug 27, 2025
Yes I'm running the standard desktop version of vs-code, installed from snap.
I'm not certain I've understood the question here but:
If I open dev tools via 'dart devtools', open the chrome debug console I get:
If I then clear the console and enter the url into dev tools so it can connect I see:
If I select 'Toogle Dev Tools' from the vs-code menu I see (as noted before):
Any attempt to launch the widget insepctor from the vs-code dart debug bar results in no output to the dev tools console.
If I clear the dev tools console and then launch a debug session I see:
which is the below exported console output.
bsutton commentedon Aug 27, 2025
The markdown preview works fine in vs code.
bsutton commentedon Aug 27, 2025
I'm not using an ssh/remote workspace. The folder for the project is loaded off my local disk.
DanTup commentedon Aug 27, 2025
@bsutton thanks for confirming. I still can't repro this, however the new E2E tests that use Playwright started failing a few days ago, and appear to be doing so consistently. The screenshot looks suspiciously like yours:
Interestingly, both you and that bot are on Linux, so I wonder if that might be related.
I've filed Dart-Code/E2E-Tests#4 for that issue and I'll see if I can figure out what changed around 3-4 days ago that made it go from 100% green to 100% red in case it might be the same here.
bsutton commentedon Aug 27, 2025
Only inconsistency is that I reported this 2 weeks ago against flutter dev tools but you are saying that the e2e only started failing 3-4 days ago.
DanTup commentedon Aug 27, 2025
I somehow missed your earlier comment with this:
I wonder if this might be related?
Yeah, that's what makes me unsure. I was thinking maybe there could be something that the GitHub runner picked up later than your machine, however based on my debugging in that issue, it seems like it might be tied to a Flutter change which I think rules that out (I'll continue to try to bisect it to a single commit though).
I remember in the past we had some issue on Linux with a GPU driver, and wonder if this could be similar. I found the issue at #4855 but the error in the console is very different (and it at least made some attempt to render something, whereas for you it seems like it hasn't - although from the console it seems like the DevTools code is definitely running).
28 remaining items
DanTup commentedon Jul 28, 2026
Friendly ping! I've not been able to repro this any more and suspect it may be fixed. Please let me know if you can still repro this. Otherwise, I'll let the bot close it after no replies for a while. Thanks!
github-actions commentedon Aug 18, 2026
This issue has been marked stale because it is tagged awaiting-info for 20 days with no activity. Remove the stale label or comment to prevent the issue being closed in 10 days.
Arkh74278 commentedon Oct 6, 2026
Adding data points to this issue — we did a deep elimination on Windows and it's still reproducible on current versions. Happy to provide more diagnostics.
Environment
bin/cache/flutter.version.jsonintact)Symptom
The embedded DevTools pages (tried both sidebar and "beside" webviews, and the debug-toolbar button) stay blank/gray forever. No DevTools UI ever renders. The same DevTools build opened in a regular Chrome on the same machine (
dart devtools+http://127.0.0.1:<port>/inspector?uri=...) loads and renders fine, and connects to the app.What we ruled out
dart devtools --machinestarts, serves HTTP 200; DTD alive;vm.registersucceeds in the DTD log.server.started, and the DevTools server receives connections when pages are open.versionfile issue (extension 3.145 readsbin/cache/flutter.version.json, which is valid).Code\Cache,CachedData,Code Cache,GPUCache,Service Worker, removed the obsolete 3.144.0 extension folders, rebooted the PC — panel is still blank.--disable-features=LocalNetworkAccess,PrivateNetworkAccessRespectdoes not change anything.Observed in the main-window DevTools console when the panel opens
While the blank panel is open there are zero established TCP connections from the webview to the DevTools server — the iframe never starts fetching. Other extensions' webviews in the same window (which don't load
http://127.0.0.1resources cross-origin) render fine.Question
Given Chrome 142+ Local Network Access enforcement for subframe navigation/fetches to
127.0.0.1from a non-local origin (vscode-webview://), does the extension have plans to serve the embedded DevTools frame in a way that avoids cross-origin private-network requests (or any other workaround) for VS Code builds whose Chromium saysUnrecognized feature: 'local-network-access'while still blocking? Right now the only working workaround isdart.devToolsLocation: external(browser), which loses the embedded experience.DanTup commentedon Oct 6, 2026
@Arkh74278 the issue you're seeing is a bit different to what was reported here. You're hitting a new bug in VS Code - see #6209 and microsoft/vscode#339079.
It's fixed in the upcoming v1.141 of VS Code. See #6209 (comment) for the workarounds I know of.