Map.build panicking at runtime 'attempt to create unaligned or null slice' about bevy_ecs_tilemap HOT 5 CLOSED

You are right, the Bevy sprite example gives the same error, so apparently the issue is on my end. Thank you for looking into it though. I'll close the issue for now and update if applicable.

from bevy_ecs_tilemap.

Can you run this with:
RUST_BACKTRACE=1?

Also what does your Map::new look like?

from bevy_ecs_tilemap.

Thank you for your work and your quick reply!

This is the stack backtrace of the unmodified iso.rs example:

stack backtrace:
0: rust_begin_unwind
at /rustc/1.51.0/library/std/src/panicking.rs:493:5
1: core::panicking::panic_fmt
at /rustc/1.51.0/library/core/src/panicking.rs:92:14
2: core::panicking::panic
at /rustc/1.51.0/library/core/src/panicking.rs:50:5
3: spirv_reflect::convert::ffi_to_block_variable
4: <alloc::vec::Vec as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
5: spirv_reflect::convert::ffi_to_block_variable
6: spirv_reflect::convert::ffi_to_descriptor_binding
7: spirv_reflect::convert::ffi_to_descriptor_set
8: <alloc::vec::Vec as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
9: spirv_reflect::ShaderModule::enumerate_descriptor_sets
10: bevy_render::shader::shader_reflect::::from_spirv
11: bevy_render::shader::shader::Shader::reflect_layout
12: core::ops::function::impls::<impl core::ops::function::FnOnce for &mut F>::call_once
13: <alloc::vec::Vec as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
14: bevy_render::renderer::render_resource_context::RenderResourceContext::reflect_pipeline_layout
15: bevy_render::pipeline::pipeline_compiler::PipelineCompiler::compile_pipeline
16: bevy_render::draw::DrawContext::set_pipeline
17: bevy_render::pipeline::render_pipelines::draw_render_pipelines_system
18: <bevy_ecs::system::into_system::FunctionSystem<In,Out,Param,Marker,F> as bevy_ecs::system::system::System>::run_unsafe
19: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
20: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
21: async_task::raw::RawTask<F,T,S>::run
22: async_executor::Executor::try_tick
23: std::thread::local::LocalKey::with
24: <bevy_ecs::schedule::executor_parallel::ParallelExecutor as bevy_ecs::schedule::executor::ParallelSystemExecutor>::run_systems
25: <bevy_ecs::schedule::stage::SystemStage as bevy_ecs::schedule::stage::Stage>::run
26: bevy_ecs::schedule::Schedule::run_once
27: bevy_winit::winit_runner_with::{{closure}}
28: winit::platform_impl::platform::x11::EventLoop::run_return
29: winit::platform_impl::platform::x11::EventLoop::run
30: winit::platform_impl::platform::EventLoop::run
31: winit::event_loop::EventLoop::run
32: bevy_winit::run
33: bevy_winit::winit_runner_with
34: core::ops::function::Fn::call
35: bevy_app::app_builder::AppBuilder::run
36: iso::main
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
Segmentation fault

I didn't modify the code of the example, so the lines look like this:

19: let mut map = Map::new(Vec2::new(2.0, 2.0).into(), Vec2::new(8.0, 8.0).into(), Vec2::new(64.0, 64.0), Vec2::new(640.0, 1024.0), 0);
31: let mut map = Map::new(Vec2::new(2.0, 2.0).into(), Vec2::new(8.0, 8.0).into(), Vec2::new(64.0, 64.0), Vec2::new(640.0, 1024.0), z + 1);

I've been tinkering with the code as well, and if I comment out the map.build(); line it runs fine (but obviously not much exciting happens).

from bevy_ecs_tilemap.

Can you run the bevy sprite example? The backtrace indicates that the pipeline reflection is failing which is a little odd and makes me think the spir-v code generated for the shader is somehow different on your machine.. 🤔

from bevy_ecs_tilemap.

Thank you! Hope you can get this resolved!

from bevy_ecs_tilemap.