Stuck with "Configuring project: Saving open files" #522
Comments
|
In my experience, this happens when some process is running on the background (e.g., VSC) and cmake is literally stuck (waiting for a lock or such?). Shutting down the new instance of VSC, killing ghost processes and restarting resolves the issue. |
|
Sorry for the delay. Hmm... "Saving open files" appears during preparation for running CMake configure, including starting up a new CMake Server instance. It's a bit misleading. It will appear even if no files are open/unsaved. Newer releases should clarify this message. If you increase the output logging level via |
|
I have the same issue. There is no VSC instance running other than the very first one launched after boot. This happens when using VSC inside WSL. Happens whe:
This is the extensions log when set to |
|
Is there anything else we can do to help debug this issue? |
|
Sorry for the delay (again). Without being able to reproduce the issue, I can't do much. As for debugging it, you could literally attach a debugger via the devtools. Set a breakpoint around the offending message and see what happens? |
|
@vector-of-bool I would gladly help with this, but I have absolutely no idea how to do it without a jump start guide. I open the devtools and I have no idea where to go. (I think this is a general issue: many communities who would be interested in having VS Code extensions don't have the skills to cook them up. I would love to see a CodeXL extension, but the entire process is just alien.) |
|
I had this issue as well and, apparently, I just managed to solve it by disabling 'Configure On Open'. On my case, it only ever appeared when I started/restarted the workspace and CMake tried to configure itself automatically. |
|
I recently installed Windows 10 1809 (finally the update succeeded) which naturally has new WSL tweaks. Anyhow, I still got Configure On Open set up, and things are working as expected now. As far as I am concerned, the issue may be closed, thought @jeanga might also want to comment. |
|
I also see this issue. I'm using Windows 1803. Rebooted PC so that no other processes running. CMake/Build output window shows: |
|
I fixed my instance of this problem by executing command: |
|
Ok to close this issue. I could not reproduce with a recent version of the tools. |
|
I have seen the problem in the last couple of days but I can't give a recipe to reproduce it. |
|
I am facing the same issue. Stuck with Configuring project: Saving open files. |
|
I repro this symptom 100% when I open the same folder in another VS Code instance (or VS Code and VS Code Insiders)...not sure if it's a different issue or not. |
|
@sean-mcmanus I think there may be multiple issues separately at play here. Having multiple instances of VS Code on the same folder sounds like another way to have multiple cmake-servers handling the same folder. Sometimes I do catch VS Code running in the background long after I close the window, and I've found that the cmake-server instance the extension spawned fails to shutdown and keeps the IDE process alive. Naturally, this is the warmbed of opening another instance onto the same folder. However with a previous Windows version (1803?) I could 100% repro the issue on a brand new folder inside WSL. |
|
I have the same issue for about one year, and I found a temporary solution: Set "Cmake:Generator" with But it may only work on my computer. how I try to solve the problemThis problem existed on my computer for long time, but, in the past, it can be solved by restarting vs-code after deleting the Today I tried restore default settings, and then set Then the process was stucked. I found the string I was worried that my expression was not clear, so I recorded a GIF of the operation:
I hope that the information I provide can help you to solve this issue. 😂 Platform and VersionsOS version: Ubuntu 16.04 |
|
Now that the extension activates on the existence of CMakeLists.txt anywhere in the folder, this is easier to repro. It actually repros on this very repo now. |
|
The repro on our folder is a different case. |
|
You can also try using the |
|
I'm dealing with this issue on a large code base. It suddenly started happening and I'm not able to fix it. E.g. restarting computer, removing git ignored files, changing communication mode. Configuring CMake takes a while because it has to download dependencies too and without a log, I don't know if it's actually working. Edit: Removing the build folder fixed it. Maybe it got stuck reading something in there. |
|
Just to have as many clues as possible when we get to fixing this. |
|
Ran into the same issue... strangely, I opened CmakeGui.exe and re-generated on the same folder than the one in VsCode and it unfreezes vscode everytime... If that can help troubleshoot... |
|
Had the same issue. In my case it was caused by me setting the installation directory to be below the build directory ("cmake.installPrefix": "${command:cmake.buildDirectory}/package"). Maybe this helps tracking it down, probably this caused some circular dependency? |
|
Yep, I think I have this problem. I'm using Ubuntu 20.04.2 LTS, cmake version 3.16.3, gcc 9.3.0, VS Code 1.55 . There appear to be numerous ways of getting the stuck 'Saving open files' dialog. I've pretty much given up on the CMake extension because of this. |
|
@mderouss, can you hard code the paths in the settings? Just to see if any variable use in the settings is causing this circular dependency. See the pattern that @OliverHaag is using above and avoid it. We will investigate and address this "Saving open files" hang. We already fixed one scenario of this for 1.7 but I don't think it's what you are hitting. |
|
Hi Andreea,
Thanks for the response :) OK, I'll investigate along the lines you suggest
and get back to you, hopefully in the next 24 hours ( it's a public holiday
in the UK right now, I have a few commitments ). There's nothing commercial
going on here, so if necessary I can just zip up a workspace and send it to
you ( just promise you won't do a code review :) ).
Regards,
Mark
…On Mon, Apr 5, 2021 at 7:56 AM Andreea Isac ***@***.***> wrote:
@mderouss <https://github.com/mderouss>, can you hard code the paths in
the settings? Just to see if any variable use in the settings is causing
this circular dependency. See the pattern that @OliverHaag
<https://github.com/OliverHaag> is using above and avoid it. We will
investigate and address this "Saving open files" hang. We already fixed one
scenario of this for 1.7 but I don't think it's what you are hitting.
In order for us to have as many repro scenarios as possible, it would help
if you confirm what happens if you change your settings and if using no
variables in settings doesn't help then maybe you can share your project
entirely?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#522 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AILEP2SDWW4KWP753ULH7FLTHFNIFANCNFSM4FRTMAIQ>
.
|
|
I believe we fixed this in 1.7.0. If you continue to hit this issue, please let us know. |
Brief Issue Summary
When trying 'any' cmake tools task, I get a notification "Configuring project: Saving open files" open that never closes (needless to say, I have no unsaved open files)
Expected:
Proceed with the task : CMake: Build
Apparent Behavior:
Nothing happens except the notification remaining.
CMake Tools Log
Empty CMake/Build log
Developer Tools Log
Platform and Versions
Other Notes/Information
PlatformIO is also installed.
The text was updated successfully, but these errors were encountered: