-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Extension host terminated unexpectedly 3 times within the last 5 minutes. #109
Comments
Hi, It would also be interesting if this is somehow related to one of your folder/projects. To my understanding there are very few Linux users for dezog. Most are on Windows or macOS. |
Hi Maziac Can you suggest a way to debug/log further. Maybe there's a file type that's triggering the issue or some other extension that is getting in the way. I'll see if I can find out how to disable all extensions except yours to see if it's a project file issue |
Ah ha - Found something while gradually turning on extensions amiralizadeh9480.laravel-extra-intellisense This instantly fires the error when I enable it |
Hmm, I also googled a bit for this error. (E.g. here similar issue: microsoft/vscode#176562 |
Happy to close this issue as a workaround has been provided and the root cause has shifted in direction. I wasn't able to replicate the error in other PHP/Laravel repo's so there must be something specific that is causing this but I don't have anything further to go off. composer.json (might provide clues for future explorers) {
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"require": {
"php": "^8.0.2",
"guzzlehttp/guzzle": "^7.2",
"laravel/framework": "^9.19",
"laravel/sanctum": "^3.1",
"laravel/tinker": "^2.7",
"league/flysystem-aws-s3-v3": "^3.0"
},
"require-dev": {
"fakerphp/faker": "^1.9.1",
"laravel/pint": "^1.0",
"laravel/sail": "^1.0.1",
"mockery/mockery": "^1.4.4",
"nunomaduro/collision": "^6.1",
"phpunit/phpunit": "^9.5.10",
"spatie/laravel-ignition": "^1.0"
},
... package.json "private": true,
"scripts": {
"dev": "vite",
"build": "vite build"
},
"devDependencies": {
"axios": "^1.1.2",
"laravel-vite-plugin": "^0.6.0",
"lodash": "^4.17.19",
"postcss": "^8.1.14",
"vite": "^3.0.0"
}
} List of installed extensions
(5 theme extensions excluded) |
Do you have a launch.json in .vscode folder? |
OK, I was just curious if there is something dezog related in it. |
I am also experiencing this issue. I cannot tell exactly when this started, I have not used dezog in a while, so it probably updated but I did update to the latest CSpect version 2.19.2.1. I have noticed that once the error occurs I cannot even run the task to launch CSpect. The task does not have much in it
DeZog Version: 3.2.2 When the extension host crashes and restarts the following message is in the
|
Could you maybe go back to dezog 3.1 for a while to see If the problem exists there, too. |
I went back to version 3.1.0 and so far so good. Here is my VSCode version information Version: 1.76.1 (user setup) |
I do not see the "extension host error", but I was now able to reproduce the problem taylorza reported with the tasks. This is somehow strange. Dezog has no relationship to the tasks. It does not use them or read them or whatever. |
Maybe it is related to some update in vscode itself. Need to check if older versions also show this behavior. |
As an additional test, I upgraded DeZog to 3.2.2 and the problem returned. |
Could you maybe test 3.2.1. I added a few packages in 3.2.2. |
I did a quick test this morning and I could not reproduce the issue with 3.2.1. And just for my own sanity, I retested 3.2.2 and I could reproduce the issue. |
👋 , in VS Code it is possible to start it in a way to produce a native crash dump. Curious if people can try to see if a crash dump is being produced, which then we in VS Code can also use to see if we could do something about it. The steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues explain the process. |
I was now able to reproduce this. |
Please retest with attached version. I exchanged the graphviz package. Could you please also check if the flowchart and callgraph is working for you. |
It looks good. I will get setup to test the reverse engineering and callgraph capabilities and let you know, but so far 3.2.3-rc2 is looking good. |
Could you please also test this version: |
3.2.3-rc3 looks good |
I released 3.2.3 to marketplace. Please let me know if it works. |
It looks like it is working as expected. Thank you! |
Yep me too. Had this running for about 40 minutes with no issues, thanks |
Thanks for testing. |
Type: Bug
This error just appeared one day. It was identified by the steps used in Extension Bisect and disabled.
Extension version: 3.2.2
VS Code version: Code 1.76.0 (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:25:16.105Z)
OS version: Linux x64 5.19.0-35-generic snap
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: