-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
generate tons of big core dump files on remote server #10359
Comments
Yes, the field_for_lambda_capture crash is known and the fix will be available in our pending 1.14.0 (pre-release). |
The fix is available with 1.14.0 (pre-release): https://github.com/microsoft/vscode-cpptools/releases/tag/v1.14.0 |
Hi @sean-mcmanus . It seems that those core dump files were not only caused by the field_for_lambda_capture crash, as I still found some cores after upgrading the plugin to version 1.14.0 in dir ".../.vscode-server/extensions/ms-vscode.cpptools-1.14.0-linux-x64/bin". GDB backtrace again:
|
I created #10507 to track that different crash. |
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
I'm a server developer. I use vscode's Remote-SSH to login my remote server and then edit code, gdb attach to my processes, etc. It was found that the extension of cpptools (specifically ./cpptools-srv)generate tons of core dump files (150GB totally within a month). The core dump files' directory is: ~/.../.vscode-server/extensions/ms-vscode.cpptools-1.13.7-linux-x64/bin. Note that the version of cpptools is 1.13.7. Now I have upgraded to version 1.13.9, but I haven't try out version 1.13.9. This problem severely hampers my daily work. I repeatedly clean up these files, but shortly afterwards they would take up all the space of my hard drive.
Expected behavior:
No core dump file generated.
Configuration and Logs
Other Extensions
No response
Additional context
I use command 'gdb ./cpptools-srv core.23028' to analyse these core dump files:
I try to upload a zip of core.23028 to help you guys debug, but it's 118MB too big to be allowed to upload. Maybe I can send it to you via email.
The text was updated successfully, but these errors were encountered: