Closed cartok closed 7 months ago
I wonder why only the first vscode instance keeps logging, while the second one just finishes, it's propably designed to allow some special interaction between vscode instances?
We have a singleton implementation for running instances, basically the first instance will act as a server and if new instances are launched they will connect to this server to check if they can be merged, if yes then instead of creating a completely new process tree the new instance will just be a child window of the first instance. Hence you see the logs cut off in the second instance after the merge happens.
Can you check if the crash repros with our insiders version as well https://code.visualstudio.com/insiders, you can avoid passing --crash-reporter-directory
. The crashes should be available in .config/Code - Insiders/Crashpad
Thanks @deepak1556 On the insider version, two or more windows open, but only one is usable. I recorded a short 5 min video to demonstrate the issues and uploaded it here: https://www.youtube.com/watch?v=FwQp6InxCb8
This is the crashpad: vscode-issue-203310-crashpad-1.zip
Hey @deepak1556, this issue might need further attention.
@cartok, you can help us out by closing this issue if the problem no longer exists, or adding more information.
I don't experience this issue anymore.
Hello, I hope this is the right place.
Something makes it that opening multiple vscode instances crashes all instances when using wayland. I tested it by opening two windows, as soon as I open the second one both crash. Sometimes I the second window works once but when I close and open it again the crash happens.
I see this issues propably since a year, I did not want to spend time with it and switched to Xwayland thought it would get fixed cause it's quite a problem if you can not open more than one vscode instance at a time. Is it just me who has this issue - Should I ask the question in the arch community?
There seem to be two problems. Leftover lock-files (can no longer reproduce right now) and issues with the GPU cache or something. When I delete
.config/Code/GPUCache
and.config/Code/Crashpad/pending
I am able to launch two windows I thought, but not does not always help, maybe sometimes I have to delete even more like the whole folder more cache related dirs.The flags I start vscode with are
--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations
and have set"window.titleBarStyle": "custom"
.I used
code --log debug --verbose
causecode --crash-reporter-directory
did not work, I think it is only an option to debug crashes that happen from inside the one instance. I wonder why only the first vscode instance keeps logging, while the second one just finishes, it's propably designed to allow some special interaction between vscode instances?System info:
I use the APU of an Intel i9-9900k, not the NVIDIA card listed below (sway still explodes with nouveau). I don't know if it matters or not, but I tested with and without
options i915 enable_guc=2
and I tested onlinux
andlinux-zen
kernel. It does not affect the situation.Logs
The log of the second (causing) editor - Crashpad (pending lock files)
Could not reproduce it. Will try again later. Also saw some vscode crashpad processes hanging around, when no vsocde instances are running.
The log of the second (causing) editor - Sandbox (GPU Cache)
The log of the first editor
Another suspect log from the first editor which I can't reproduce tho
Another thing
Don't know if it is related, could be, I expected this to vanish some day but it still persists.