Integrated Console stops responding #175027
Assignees
Labels
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
info-needed
Issue requires more information from poster
Comments
dfdumaresq
changed the title
connor4312
added
bug
|
I tried to repro this by adding redux-logger to connected-react-router's basic demo and things worked fine, both on Insiders and stable
(btw, the upcoming release next week will make colors works 😉) Can you please either:
/jsDebugLogs |
|
Please collect trace logs using the following instructions:
|
VSCodeTriageBot
added
the
info-needed
|
Will do. Thanks! |
|
@connor4312 - The debug file is too big (25 MB allowed, 31 MB attempted to upload). Do you have an email address I can send it to? |
|
Yep, connor@xbox.com. OneDrive etc. links also work 🙂 |
|
Thanks, it's off. - Actually, it was rejected. Too large. Will try another service. |
|
@connor4312 - You should have it now through maildrop (iCloud). |
|
Thanks! Did you recall seeing any errors in the Console when running Toggle Developer Tools? |
|
Sorry, I forgot to include them. I'll send you fresh logs and screenscrapings the next time I get the crash. |
|
I've sent the full crash dir to your mail account, Connor. |
|
Sorry @connor4312 - had trouble again with the file size. Here's a OneDrive link. Let me know if you have any issues. |
|
Oh, the extension host crash is why you saw the freeze. The debugger won't exist at that point, and we don't really handle ext host crashes well in debug land right now. This is probably the same as #174541 |
|
Thanks Connor, I'll follow the link above. |
|
I'm curious if my suggested fix at #174541 (comment) solves the issue for you or not |
|
Hi @connor4312, I did not try your suggestion, but will add it to my launch.json now. I got buried in my work and just tried to stop using the JS Debugger, because determining details about the extension host seemed like too much work. :/ Perhaps, your suggestion will help. Let you know. |
|
@connor4312 - I've added your suggestion. But don't see any change.
I noticed this at the top of the Debug output for Chrome: So I've instead disabled the Nightly Javascript Debugger and enabled Debugger for Chrome (Nightly) On launch I now see console errors like these. I will run it until it crashes and send a log. |
|
Apologies, it should be |
|
Ok, I've changed the property to false as you recommend. Still seeing all the red, but will let you know how it goes. |
|
Yea, I have no idea where that's coming. Searching all of Github for |
|
I've switched Javascript Debugger extensions back to Javascript Debugger (Nightly). The errors are gone, and I can breakpoint now. As I've reported before: |
|
With that error, I think this is the same as #146002. Sorry for not making the connection earlier. If you have a repo or some specific code you can share that reproduces the issue, I would really like to see it. |
|
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
|
@roblourens - what assurances can I give my director before offering you a look with our private repo? I don't mean to sound arrogant, I'm just wondering if mgmt will be comfortable with sharing and I don't see an easy way to give you a reproducible example. Also, I'm running our management-console web app to handle the front end UI, which is my part in this. Anyway, I'm the only programmer it seems that is using the debugger. (shrug), so it's probably a non-starter. |
|
Console has stopped responding. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
and others
Type: Bug
From VSCode Insiders,
const middlewares: Middleware[] = [routerMiddleware(history), ...storeMiddleware];
if (process.env.NODE_ENV === "development") {
middlewares.push(logger);
}
Notice after initial output terminal is no longer responsive. Cannot clear or scroll.
E.g.
VS Code version: Code - Insiders 1.76.0-insider (Universal) (5454665, 2023-02-21T05:23:24.160Z)
OS version: Darwin x64 22.2.0
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Extensions (3)
A/B Experiments
The text was updated successfully, but these errors were encountered: