Repository navigation
DevTools tools mostly appear blank #462
Description
Activity
Are you having this on a local site, or a site with self-signed HTTPS certificate?
I'm having this problem a lot on such sites.I resolved this issue.
Root Cause
Ourrspack.dev.jssets devtool:"inline-source-map". In dev mode this makes the unminified settings2.bundle.js grow to ~27MB, including one giant base64-encoded source map inlined at the end of the file. When DevTools attaches, it must synchronously parse this huge inline blob. Chromium DevTools on macOS handles such oversized inline resources noticeably worse than on Windows, causing the ~20s freeze; Safari (WebKit) is unaffected due to a different implementation.Fix
Change devtool:"inline-source-map"to devtool:"eval-source-map"in rspack.dev.js:Source map data is no longer packed into a single giant base64 blob; it is split per module and inlined within each module's own eval() wrapper
Total source map data volume is roughly unchanged (bundle file size stays about the same), but DevTools can process it incrementally per module instead of freezing on one massive blob
module.exports = (env = {}) => { const config = merge(common(env), { entry: { ...common(env).entry, ...(fs.existsSync(path.resolve(__dirname, "./src/test/index.tsx")) ? { test: "./src/test/index.tsx" } : {}), }, mode: "development", devtool: "eval-source-map", output: { chunkFilename: "[name].bundle.js", }, optimization: { minimize: false, minimizer: [], } }); config.plugins[1] = new ESLintPlugin({ extensions: [`jsx`, `tsx`, `ts`], configType: "flat", failOnError: false, failOnWarning: false, emitError: true, emitWarning: true, overrideConfig: { "rules": { "no-debugger": 0 } } }); return config; };
Thank you for reporting this bug. The team is investigating the issue and I'll share updates soon.
- marked There is a probability that the panel will freeze and not display network, source code, and other panels #464 as a duplicate of this issue
on Sep 21, 2026 - marked Dev tools tabs stop rendering/updating on local sites with self-signed cert #463 as a duplicate of this issue
on Sep 21, 2026 Hi everyone, thanks for your patience! There's a fix for this bug in Edge Canary 156.0.4296.0. Please try it out and let us know if you're still seeing the same issue.
Reacted by Chris DuffI am still experiencing this issue on version 156.0.4285.0.This behavior originally started occurring for me in version 153. Even though it was mentioned that the bug was fixed in version 156, the DevTools panels (Console, Sources, and Network) still appear completely blank.Disabling extensions or resetting DevTools settings did not resolve the problem. Please consider reopening the issue or investigating further.
Reacted by Chris DuffEugene (@FlexIDK) can you update to Canary version
156.0.4296.0or newer and try again?, version156.0.4285.0does not contains the fix.Vidal Ortega (@vidorteg) Hi! I have updated to Canary version 156.0.4300.0 as requested, and I can confirm that everything works correctly now. The DevTools panels are no longer blank.
Thank you for the fix!Reacted by leahtu and Vidal OrtegaVidal Ortega (@vidorteg), leahtu
The bug has returned in the latest Canary build (version 156.0.4309.0).
Broken functionality:
• Tab switching: Switching between tabs does not work (the tabs appear completely blank).
• Element selection: Selecting elements using the selector tool is broken.
• DevTools freezing: The Developer Tools panel freezes / hangs up completely.Reacted by Chris DuffThank you for letting us know - we're investigating this further. Sorry about the inconvenience
Reacted by Chris DuffVidal Ortega (@vidorteg), leahtu The bug has returned in the latest Canary build (version 156.0.4309.0). Broken functionality: • Tab switching: Switching between tabs does not work (the tabs appear completely blank). • Element selection: Selecting elements using the selector tool is broken. • DevTools freezing: The Developer Tools panel freezes / hangs up completely.
Eugene (@FlexIDK) We found a Chromium issue that may be related: the Elements panel goes blank and the element selector stops working after multiple page reloads. Does that match what you’re seeing in Canary?
leahtu
I have investigated this issue further and can confirm that it persists in recent Microsoft Edge versions. Specifically, I tested and reproduced the DevTools freezing behavior in Edge 157.0.4320.0 and 154.0.4258.62.Interestingly, the issue does not occur in Google Chrome (tested on 154.0.8037.98 and older versions), where DevTools works completely as expected under identical conditions.
Environment Details & Observations:
- Tech Stack: Nuxt 4 + Vue 3 running on local host (
http://127.0.0.1:3000/). - Production vs. Development: The DevTools freeze only happens in development mode. When running the production build of the project, DevTools functions perfectly.
- Nuxt Version Regression:
- If I downgrade Nuxt to version 4.4.8, the bug disappears completely.
- Starting from version 4.5.0 and later (in dev mode), Edge DevTools consistently freezes.
- Clean Project Baseline: When generating a fresh, minimal boilerplate project via
npm create nuxt@latest, the issue cannot be reproduced. It seems related to a specific dependency or configuration interplay in larger projects that was introduced in Nuxt 4.5.0. - Browser Regression: The issue is absent in Edge 152 (and older) as well as any Chrome version, regardless of the Nuxt version used. The breakage strictly started appearing from Edge 153 onwards.
Attached Files:
To help narrow down what exactly might be triggering this in Edge post-v153, I have attached the
package-lock.jsonfiles for both states of the project:package-lock_4.4.8.json(Working state)package-lock_4.5.0.json(Broken state)
Hopefully, a diff between these dependency trees can point toward the specific package causing the conflict with newer versions of Edge DevTools. Let me know if you need any additional logs or isolated reproduction steps!
Reacted by Chris Duff- Tech Stack: Nuxt 4 + Vue 3 running on local host (
Here too, or at least take a lot of time to open and when opened, I can't maximize. And my settings isn't opening.
Eugene (@FlexIDK) thank you for all the details. We're still investigating.
tabathambosch can you share the edge://version you're on? Are you using DevTools undocked in a separate window when you're seeing these issues (can't maximize or open settings)? If you dock DevTools, do you still see the same issue?
I’m experiencing a similar issue on macOS with Edge 154.0.4258.62.
My project uses Vue 3, Vite, and TDesign Vue Next. Edge DevTools freezes and its process reaches 100% CPU, while the page process remains around 0.1%.
What I’ve tested:
- The issue occurs in development mode; the production build works normally.
- Replacing ViteSSG with a standard Vue
createAppentry does not resolve it. - A minimal diagnostic page reproduces the issue by importing
tdesign-vue-next, without registering it or rendering any TDesign components. - TDesign versions 1.20.9, 1.20.8, and 1.20.7 all reproduce it.
- Vite versions 8.3.3 and 8.3.1 both reproduce it.
- The diagnostic page runs without the
vite-plugin-vue-devtoolsplugin. - Disabling Enable JavaScript source maps in Edge DevTools resolves the freeze.
The Vite-served TDesign dependency response contains an inline source map and is approximately 9 MB. This suggests source-map processing may be involved, although I haven’t isolated the exact cause.
Hoping this issue could be resolved soon...
I'm also experiencing this issue, running Edge 154.0.4258.62. leahtu, I'm running DevTools docked, but I think the cause of the issue might exist elsewhere. If I disable source maps in the in DevTools settings, everything works as expected. As soon as I enable source maps again, I get blank tabs inside DevTools, no network requests displayed, page won't reload when pressing F5 and can't get into DevTools settings.
Reacted by Chris Duff+1 禁用JavaScript源映射正常运行,开启则卡顿 Edge 155.0.4283.45
21. 我也遇到这个问题，运行的是Edge 154.0.4258.62。我用的是底座运行DevTools，但我觉得问题可能出在别处。如果我在开发工具设置中禁用源映射，一切正常运行。一旦我重新启用源映射，DevTools里出现空白标签页，没有显示网络请求，按F5页面无法重新加载，也无法进入DevTools设置。
OS: macOS v26.6
Edge: Version 153.0.4234.48 (Official build) (arm64)
The Edge DevTools are currently experiencing an issue in which tools appear blank. The Console, Sources, and Network tools all show no data. Unless I hide the "Networ" tab.