![]() Updated to the latest version, now all my opened windows and files are gone and the "recent" list is empty. Meanwhile I know for sure there is a folder with all cached project entries kept at $HOME/.config/Code/User/workspaceStorage that keeps track of ever opened projects & workspaces. I just have recently updated it from v1.72 to v1.73 and all recently opened projects entries disappeared from Ctrl+R menu.įor me it happens like once in a while. I'm experiencing a similar issue but only when VS Code itself gets updated. You've added an 'info-needed' label but I've provided everything so not sure why that is there. ![]() I've output even more energy trying to provide everything you required and now that you have it you just want to leave it. Extension host with pid 1525 exited with code: 0, signal: null.Īnyway, I am not having the energy anymore to spend more time on this and also do not feel like arguing with you, sorry. Waiting for extension host with pid 1525 to exit. Starting extension host with pid 1525 (fork() took 2 ms). Extension host with pid 616 exited with code: 0, signal: null. Starting extension host with pid 616 (fork() took 1 ms). Please make clear exactly what it is you require since as far as I can see I have provided what you asked for. No-one else reported this either or was even able to reproduce it after reporting it, without giving them my specific project.but it was still an issue. Given no one else reported this and I feel the amount of time I have invested here is reaching its limits. If you want log files from the opening the following day after a problematic shut down then I don't see why you don't ask for them, but until now I have provided exactly what you asked for. ![]() I have no idea why you're suddenly pre-occupied with how files are opened at the beginning of the day on a day where the files opened with no issue, rather than the part where it shuts down causing the issue the following day. These are the logs from the problematic SHUTDOWN which is what you asked for. "find the session from shutdown and open main.log" The questions you're asking seem to be unrelated but I explained them above nonetheless. Where did I say the logs were not related to the issue? If you're not looking at the parts about the SHUTDOWN then the problem is not with the logs themselves. Am confused, how are the 2 logs you sent not related to this issue?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |