-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network tab freezes VSCode when displaying base64 image encoded strings #5973
Comments
The commands to open specific pages only appear when you have an active debug session (because they can only be loaded with a VM Service connection). You'll only see the generic "Open DevTools" command if you don't have a session. It's not clear if you had one open or not?
There's not a lot of interaction between VS Code extensions and the terminal, so if this isn't working (and persists after a reboot) there might be something wrong with VS Code (perhaps something got corrupt during the update because it didn't close cleanly?). Are there any errors listed if you click Help -> Toggle Developer Tools and click on the Console tab? There are some VS Code commands to get logs:
I don't know of any of them will contain anything useful though. If not, if you're able to reproduce this at all it might be useful to run VS Code with the crash reporter directory set to see whether it captures anything that we could report to VS Code (in theory, extensions should not be able to crash VS Code, so even if DevTools we're triggering it, there might be an underlying VS Code bug). |
Hi!
I was checking out the network tab to inspect some request/response objects (just opening the fields here and there to read inside), when at some point, VSCode froze, prompting me to Re-open, close, or wait.
I clicked wait the first time, then re-open the 2nd time.
It closed the window, opened the small "Updating VSCode window" for 10sec, before not re-opening VSCode after 2min.
I clicked on the VSCode icon to launch it, it worked right away, I waited a minute so everything can get initialized, but there was a notification about the terminal not closing correctly and something like "pty needs to restart". I clicked on restart, it wrote "restarting terminal etc" in blue in my terminal, and then the notification popped up again, so I repeated the operation 3 times before giving up and going into Terminal > Kill Terminal > New Terminal, but it immediately closes again as soon as it starts.
On the devtools side, I don't see the "Dart: Open the Network DevTools tab" anymore at all: it just disappeared from my IDE. Here is what I see:
("Dart: Open DevTools" being the one in the web browser, not in VSCode)
Further VSCode restarts didn't help, and I haven't tried restarting my PC yet in case it erases some internal VSCode logs that could be useful to know more about this issue.
As of right now, it means:
Of course I expect a PC restart to fix both issues, but I'll just wait for your answer before trying.
Let me know if you need more details on any step, I'll gladly provide everything you need!
Versions
OS: Windows 10 22H2
Flutter: 3.10.5
Dart: 3.0.5
DevTools: 2.23.1
VSCode: 1.79.2
The text was updated successfully, but these errors were encountered: