Metal debugger reports Out of Bounds Buffer Index in "general mesh slab"
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 161
Description
## Bevy version
Both 0.14.1 and main 8235daaea0e3aa930e34c57887e1ffea08a8150a.
## Relevant system information
```
SystemInfo { os: "MacOS 14.4.1 ", kernel: "23.4.0", cpu: "Apple M1", core_count: "8", memory: "8.0 GiB" }
AdapterInfo { name: "Apple M1", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
```
Metal Debugger from XCode 15.4
## What you did
While investigating an bug in an ecosystem crate, [bevy_mod_outline#](https://github.com/komadori/bevy_mod_outline/issues/44), @rparrett pointed out that the Metal debugger displayed a warning about an "Out of Bounds Buffer Index" in the "Vertex Buffer 15 - general mesh slab 0 (vertex buffer)".
I reproduced this message in Bevy's 3d_scene example so it is unrelated to any 3rd party crate. It doesn't seem to cause any problems, but I have no idea why it happens. Perhaps this is completely normal behaviour for the Metal debugger, or perhaps it is indicative of some subtle bug in Bevy/WGPU/Metal. I have spent some time investigating and discerned nothing so I am creating this issue in case any MacOS expert knows more and for posterity.
## Additional information

I don't actually own a Mac and tested this using a remote hosted machine.
Contributor guide
Assessment
This issue has not been assessed yet.