You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any usage of bevy_ecs_tilemap seems to cause the application to crash when the application window is minimized. This is reproducible using the built in map example with $env:RUST_BACKTRACE=1; cargo run --release --example map.
Backtrace below:
thread 'main' panicked at 'view entity should exist: QueryDoesNotMatch(0v0)', C:\Users\leonardmh\.cargo\registry\src\github.com-1ecc6299db9ec823\bevy_core_pipeline-0.7.0\src\main_pass_2d.rs:45:14
stack backtrace:
0: std::panicking::begin_panic_handler
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c\/library\std\src\panicking.rs:584
1: core::panicking::panic_fmt
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c\/library\core\src\panicking.rs:143
2: core::result::unwrap_failed
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c\/library\core\src\result.rs:1749
3: <bevy_core_pipeline::main_pass_2d::MainPass2dNode as bevy_render::render_graph::node::Node>::run
4: bevy_ecs::storage::sparse_set::SparseSet<I,V>::get_or_insert_with
5: bevy_ecs::storage::sparse_set::SparseSet<I,V>::get_or_insert_with
6: bevy_render::renderer::render_system
7: <bevy_ecs::system::exclusive_system::ExclusiveSystemFn<F> as bevy_ecs::system::exclusive_system::ExclusiveSystem>::run
8: <bevy_ecs::schedule::stage::SystemStage as bevy_ecs::schedule::stage::Stage>::run
9: core::mem::drop
10: bevy_app::app::App::update
11: winit::platform_impl::platform::event_loop::EventLoop<T>::run_return
12: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
13: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::send_event
14: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::move_state_to
15: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
16: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::catch_unwind
17: winit::platform_impl::platform::event_loop::normalize_pointer_pressure
18: CallWindowProcW
19: EnumChildWindows
20: IsIconic
21: KiUserCallbackDispatcher
22: NtUserDispatchMessage
23: DispatchMessageW
24: winit::platform_impl::platform::event_loop::EventLoop<T>::run_return
25: winit::platform_impl::platform::event_loop::EventLoop<T>::run
26: bevy_winit::handle_create_window_events
27: bevy_winit::change_window
28: bevy_winit::winit_runner_with
29: core::ops::function::Fn::call
30: bevy_app::app::App::run
31: core::ptr::drop_in_place<core::option::Option<bevy_render::mesh::mesh::Indices>>
I reproduced this using the latest commit on main, currently 7ed6296.
The text was updated successfully, but these errors were encountered:
At first I thought this was just a bevy problem in general, but I created a minimal bevy project (the hello_world example) and I was able to minimize the window. I then went back to my project and just removed everything related to bevy_ecs_tilemap and my application no longer crashed on minimize.
I attempted to git bisect debug to determine when this broke, but going back to the first commit that has a still working version of map.rs (1a91e7c) still crashes, though the backtrace does look different.
Any usage of
bevy_ecs_tilemap
seems to cause the application to crash when the application window is minimized. This is reproducible using the built inmap
example with$env:RUST_BACKTRACE=1; cargo run --release --example map
.Backtrace below:
I reproduced this using the latest commit on
main
, currently 7ed6296.The text was updated successfully, but these errors were encountered: