Unable to open source file #94931
Assignees
Labels
bug
Issue identified by VS Code Team member as probable bug
freeze-slow-crash-leak
VS Code crashing, performance, freeze and memory leak issues
verified
Verification succeeded
Milestone
Comments
|
@hiriumi Does this happen with all file types, not just .py? Can you run the command "Developer: Toggle Developer Tools" and check what is in the console? |
|
@RMacfarlane I checked the console and here is what I found. I wonder what I did wrong? |
|
Thanks for the info! Can you also try opening the Output Panel and checking what is in "Log (Extension Host)"? |
|
Sorry I should have attempted to open a file after I opened the developer tool. Here is what the actual error looks like. |
|
I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: |
|
@bpasero |
|
@bpasero |
|
I completely cleared all files generated by VS Code and now I'm able to open files within it. I bet there was a file (or more) that was in a bad state which might have caused the issue. I ran the following commands based on this article. This could be the VS Code (or extension?) bug because it might have generated the file that might have caused the issue although I did not take the steps to pin point the issue. I'm not familiar with debugging VS Code and I'm not sure how I can help but please let me know if there is anything I can do to contribute to the community. My VS Code is back to the original state but at least I can reconfigure it to my liking again. Thanks! |
|
I'm experiencing the same issue on Windows since today (with and without extension enabled) Version: 1.44.0 (user setup) |
|
A wrong entry in settings.json caused the problem in my case: |
|
Thanks, I had exactly the same issue! |
|
Thanks xandi, that was my problem also! |
bpasero
added
bug
|
@rebornix @alexdima I can reproduce when configuring Would be great if there was a big try-catch around editor options parsing so that we can deal with this better and e.g. show a message to the user + fallback to default options. This is probably a candidate. |
alexdima
added
the
freeze-slow-crash-leak
|
same thing happened to me and it was triggered by setting "editor.quickSuggestions": null (instead of "editor.quickSuggestions": false). to change this: windows
Mac |
This was referenced Apr 20, 2020
Closed
|
Thanks @xandi, removing
|
|
Why is this closed, if it's not fixed?? I just ran into this with the latest version of VSCode that I installed yesterday. And I didn't add the Please fix this. |
Closed
|
@lacikawiz it is marked as closed and has milestone April 2020 because 59e4b45 is already in 1.45.0-insider and will arrive in the regular release at the end of this iteration. |
|
@lacikawiz This is very concerning for me:
AFAICT VS Code does not do that. What extensions do you have installed? It appears that an extension might be doing that. |
|
I have the following extensions currently: I installed them one after the other, so I don't know which might have caused this. |
|
@lacikawiz Thank you for the extra information. I searched all of those repositories, but unfortunately, I could not find any matches for |
|
I have the same problem but when I changed it from quickSuggestions: null to quickSuggestions: false everything stopped opening including the settings. I have uninstalled VSCode and reinstalled it and it just doesn't want to open any files at all. I am going back to atom. It just works. |
|
@theblindguidedog Uninstalling will unfortunately not remove the user settings, so they will persist even after reinstalling, so the bug will reproduce again. The Insiders build has a fix available and a fix will come to the Stable build in about a week or so. We did not roll out a recovery update for the Stable build because we have found that, while the severity is critical (the editor doesn't work at all), the incidence is low. Also, VS Code had this problem since November (after doing a blame on the code), so we have shipped with this bug for 6 months, yet the issue is only reported since about 3 weeks. There appears to be some kind of extension or tutorial that is writing on behalf of / driving people to write @theblindguidedog I would like to ask why do you have that setting written in that form in the user settings? Did you follow a tutorial or an extension did that automatically? I'm asking because I would like to reach out to the extension that does this and ask them to stop doing it :). |
You saved me, man, thanks a lot :) |
|
We fixed this by opening up our settings.json file on disk
And deleting Quit VSCode, brought it back up, and we're good to go. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type: Bug
As of this morning, I'm unable to open any file. I use it on Mac and I even removed ~/.vscode to see if this error goes away. Here is the error.
Unable to open 'myfilename.py': Assertion Failed: argument is undefined or null.
This is really preventing me from using VS Code although I could use different text editor. I would like to know why this is happening possibly have a fix for it.
Thank you!
VS Code version: Code 1.44.0 (2aae1f2, 2020-04-08T08:23:56.137Z)
OS version: Darwin x64 18.7.0
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: