Skip to content
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

Bevy game occasionally crashes VS Code after being closed if it was launched from VS Code integrated terminal #13351

Closed
ArmoredPony opened this issue May 13, 2024 · 2 comments
Labels
A-Cross-Cutting Impacts the entire engine A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong

Comments

@ArmoredPony
Copy link

ArmoredPony commented May 13, 2024

Bevy version

0.13.2

[Optional] Relevant system information

OS: Windows 10
VS Code version: 1.89.1

AdapterInfo { name: "NVIDIA GeForce RTX 4050 Laptop GPU", vendor: 4318, device: 10465, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "552.44", backend: Vulkan }

What you did

I usually launch my games from integrated VS Code terminal with cargo run.

What went wrong

Upon closure of the game VS Code program starts to increase its CPU usage and RAM consumption until it crashes with "Out Of Memory" error. I haven't found any additional information in VS Code logs. There is only that "Out Of Memory" message. This crash happens occasionally once per many launches and I can not reliably reproduce it. The only thing I can tell is that it doesn't matter if the game is run the first time after it's recompiled or not.

cargo build never fails, the crash happens only after the app was closed.

I'm sorry I cannot provide any additional information. This issue might not even be related to Bevy but it is the only app that ever caused it. I will provide any additional information that is necessary and can be gathered.

Additional information

I use dynamic_linking feature and opt-level = 3 package-specific override. Linking is done with lld. I followed Bevy Setup guide.

@ArmoredPony ArmoredPony added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels May 13, 2024
@alice-i-cecile alice-i-cecile added A-Windowing Platform-agnostic interface layer to run your app in S-Needs-Investigation This issue requires detective work to figure out what's going wrong A-Cross-Cutting Impacts the entire engine and removed S-Needs-Triage This issue needs to be labelled labels May 13, 2024
@alice-i-cecile
Copy link
Member

I have never encountered this using Windows 11 and launching Bevy apps through the VSCode terminal. I would love to fix this, but I have no idea where to start looking.

@ArmoredPony
Copy link
Author

Encountered a VS Code crash after launching the game from external terminal. It required way more tries but I think at that point it's not on bevy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Cross-Cutting Impacts the entire engine A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

2 participants