bevyengine / bevyengine/bevy

VkQueueSubmit: value exceeds limit regarding current semaphore VkSemaphore, app crashes

Open
#3,237 1 comment 0 reactions 0 assignees View on GitHub
A-Rendering C-Bug C-Startup I-Crash I-Regression S-Needs-Investigation
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
4d 8m
Merged PRs (30d)
147

Description

## Bevy version

Latest main ccee658436be3d8bd721bbdda4a02f47235799da

## Operating system & version

Windows 10

## What you did

cargo run --example bevymark

## What you expected to happen

It should not crash.

## What actually happened

It crashes.

## Additional information

```
2021-12-02T14:24:44.211716Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-VkSubmitInfo-pSignalSemaphores-03244 (0x7fd092df)]
Validation Error: [ VUID-VkSubmitInfo-pSignalSemaphores-03244 ] Object 0: handle = 0xf8ce070000000002, type = VK_OBJECT_TYPE_SEMAPHORE; | MessageID = 0x7fd092df | VkQueueSubmit: value exceeds limit regarding current semaphore VkSemaphore 0xf8ce070000000002[] payload The Vulkan spec states: For each element of pSignalSemaphores created with a VkSemaphoreType of VK_SEMAPHORE_TYPE_TIMELINE the corresponding element of VkTimelineSemaphoreSubmitInfo::pSignalSemaphoreValues must have a value which does not differ from the current value of the semaphore or the value of any outstanding semaphore wait or signal operation on that semaphore by more than maxTimelineSemaphoreValueDifference (https://vulkan.lunarg.com/doc/view/1.2.141.0/windows/1.2-extensions/vkspec.html#VUID-VkSubmitInfo-pSignalSemaphores-03244)
2021-12-02T14:24:44.211813Z ERROR wgpu_hal::vulkan::instance: objects: (type: SEMAPHORE, hndl: 0xf8ce070000000002, name: ?)
error: process didn't exit successfully: `target\debug\examples\bevymark.exe` (exit code: 0xc000041d)
```

Same happens with my game, it did not do this in 91c3b210.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.