fishfolk
Crash: Windows crash on startup, very little logs
Description
On discord, @Illinore reported a crash on windows.
There are so little logs, and no panic, either app is exiting cleanly or crashing hard / early.
One thing I wonder about is gpu drivers. I wonder if the AdapterInfo log (this is missing here) could be generated by bones earlier, and possibly captured? Probably should add some more tracing throughout startup to see where this failed.
Otherwise, would be interesting to know what gpu + if drivers are up to date, and what backend wgpu tries to use (for windows, openGL or DX12?).
There is no panic, which could be a segfault due to unsafe code / or maybe c library crashing? I wonder if generating a minidump might be useful here.
To Reproduce
Reported reproducing on steam playtest builds 0.12.1 and 0.12.2 on windows.
(I cannot repro on windows).
Log Messages
The only logs from logfile:
2024-09-12T02:20:34.568169Z INFO bevy_winit::system: Creating new window "App" (0v0)
I also think setting up builds on steam such that a launch command may be used to increase log verbosity might be helpful. (Basically be able to set RUST_LOG).
I may uninstall my gpu drivers on windows see if get something similar... for science.
When running without drivers for my discrete gpu, I get this and a crash:
2024-09-14T18:55:23.916689Z INFO bevy_winit::system: Creating new window "App" (0v0)
2024-09-14T18:55:24.230129Z INFO bevy_render::renderer: AdapterInfo { name: "Microsoft Basic Render Driver", vendor: 5140, device: 140, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Dx12 }
2024-09-14T18:55:24.802936Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 10 Home", kernel: "19044", cpu: "Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz", core_count: "6", memory: "63.9 GiB" }