fix(core): Fix corner cases in initialized range tracking

Author: andyleiserson

CHANGELOG.md

@@ -83,6 +83,7 @@ Bottom level categories:
 - Zero-initialize padding (if any) at the end of a buffer allocation. This was application-visible in rare cases on Vulkan when a shader read beyond the valid range of a vertex buffer. By @andyleiserson in [#9791](https://github.com/gfx-rs/wgpu/pull/9791).
 - Fix required immediate slots calculation and remove `naga::valid::FunctionInfo::immediate_slots_used`. By @beicause in [#9725](https://github.com/gfx-rs/wgpu/pull/9725).
 - Fix `PendingSubmission` releasing its lock guards out of stacking order, which tripped `--cfg wgpu_validate_locks` on any submission. By @AdrianEddy in [#9960](https://github.com/gfx-rs/wgpu/pull/9960).
+- Fixed some cases where initialization tracking was not correct. By @andyleiserson in TBD.
 
 #### naga
 

Cargo.lock

@@ -178,6 +178,8 @@ portable-atomic = "1.10"
 portable-atomic-util = "0.2.4"
 pp-rs = "0.2.1"
 profiling = { version = "1.0.1", default-features = false }
+# Limit to versions that use rand 0.8
+proptest = ">=1, <1.7"
 raw-window-handle = { version = "0.6.2", default-features = false }
 rayon = "1.3"
 regex-lite = "0.1"

Cargo.toml

@@ -211,5 +211,8 @@ thiserror.workspace = true
 [target.'cfg(not(target_has_atomic = "64"))'.dependencies]
 portable-atomic = { workspace = true, optional = true }
 
+[dev-dependencies]
+proptest.workspace = true
+
 [build-dependencies]
 cfg_aliases.workspace = true