protonscr

ASSERT: Vulkan transfer ring buffer overflow

steamvropen bug
ValveSoftware/SteamVR-for-Linux#1006 · opened 2026-10-10 by Markosha2004 · updated 2026-10-20 · 7 comments · github
MMarkosha2004 2026-10-10 github

Describe the bug
When I try to launch VR-capable or VR-only game titles, the headset goes black, and SteamVR displays either "headset not in fullscreen mode" or "Error -203"

To Reproduce
Steps to reproduce the behavior:

  1. Launch SteamVR on beta branch
  2. SteamVR launches as expected
  3. Launch a VR game like H3VR, or, in my case, VRChat.
  4. See that headset goes black as soon as application is launched, and SteamVR displays any of the errors mentioned above.

Expected behavior
Games to launch as normal

System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!

  • Steam client version (build number or date): 1791592380
  • SteamVR version: 2.18.3 beta
  • Distribution (e.g. Ubuntu): Nobara 44
  • Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client]

runtime diag.txt

  • Steam and SteamVR logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]

steam-logs.tar.gz

  • Minidumps: [run the following command: tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]

steam-minidumps.tar.gz

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

I am also attaching two crash dumps of vrcompositor failure

"Headset is not in fullscreen mode"

crash dump vrcompositor.txt

Error -203

crash dump 2 vrcompositor.txt

Kkisak-valve maintainer 2026-10-10 github

Hello @Markosha2004, these look like some lines of interest from your vrcompositor.txt:

Sat Oct 10 2026 13:11:26.919621 [Error] - ASSERT: "Vulkan transfer ring buffer overflow; transfer size 71100!" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5502.
[...]
Sat Oct 10 2026 13:20:31.804015 [Error] - ASSERT: "Vulkan transfer ring buffer overflow; transfer size 2315040!" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5502.
MMarkosha2004 2026-10-10 github

Noted, but, unfortunately I don't possess enough knowledge to dive deeper into this.

Kind regards, @Markosha2004

Ddemolitions 2026-10-14 github

Same assert here, on the stable branch, so it is not limited to the 2.18.x beta, and on CachyOS, so it's not distribution based. The assert and the transfer size is the same 71100 bytes as in the original report.

Wed Oct 14 2026 20:40:01.265449 [Error] - ASSERT: "Vulkan transfer ring buffer overflow; transfer size 71100!
" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:5502.
Wed Oct 14 2026 20:40:01.327409 [Error] - Aborting due to fatal assertion failure.

The headset goes black, vrcompositor aborts and is not restarted, and SteamVR stays running. Only a full SteamVR restart recovers.

System

  • SteamVR 2.17.10 (stable, buildid 25330290)
  • CachyOS, kernel 7.2.9-1-cachyos
  • AMD Radeon RX 9060 XT (RADV GFX1200), Mesa 26.2.4
  • HTC Vive (original) with Valve Index controllers
  • Vive front camera enabled with Room View (enableCamera: true, roomView: 1)

Observations

  • Seen multiple times since I swapped from a RTX 2070 SUPER to the RX 9060 XT on 2026-10-05. Always 71100 bytes.
  • Was not happening on the RTX 2070 SUPER, so I suspect some kind of interaction with the RADV driver.
  • It does not need a scene application or third-party software. On 2026-10-05 it happened with no third-party overlay and no Vulkan layer loaded.
  • The last time it happened right when I closed the dashboard.
  • In every session vrcompositor logs Ring Buffer Wrapped! every 10-11 seconds, steadily, from shortly after startup until the assert. The rate is the same whether or not other overlay apps are running, so something inside the compositor seems to upload continuously through the transfer ring.
  • I'm going to try disabling Room View, and see if it still occurs, but since there is no reliable way to reproduce, it may take a while to confirm.

Attachments

JJnnovation 2026-10-14 github

a little different on my end, on the previous branch, SteamOS on PC. (This also happens on the beta and default branch)

Thu Oct 15 2026 01:03:41.852752 [Error] - ASSERT: "Vulkan transfer ring buffer overflow; transfer size 2315040!
Thu Oct 15 2026 01:03:41.914826 [Error] - Aborting due to fatal assertion failure.
Thu Oct 15 2026 01:03:59.413203 [Info] - Tracked Camera: Unexpected or not-specified number of cameras (propertyError=0, 0).
Thu Oct 15 2026 01:03:59.436867 [Error] - WaitForPendingPresent: vkWaitForPresent timed out, falling back to old behavior (1 times)
Thu Oct 15 2026 01:03:59.486638 [Error] - WaitForPendingPresent: vkWaitForPresent timed out, falling back to old behavior (2 times)
Thu Oct 15 2026 01:03:59.575217 [Error] - WaitForPendingPresent: vkWaitForPresent = VK_SUCCESS after previous failures
Thu Oct 15 2026 01:05:19.877204 [Error] - ASSERT: "Vulkan transfer ring buffer overflow; transfer size 2315040!
Thu Oct 15 2026 01:05:19.946342 [Error] - Aborting due to fatal assertion failure.

The only common factor is RADV and SteamVR itself, it could be an issue only now seen but created further back.

System

  • SteamVR previous 2.16.7
  • SteamOS Beta 3.9.2 Build 20260925.101
  • AMD Radeon RX 7800 XT (RADV GFX1101), Mesa 26.1.2
  • Valve Index

Observations

  • Ring buffer overflow transfer size 2315040 instead of apparently more common 71100.
  • Same amount happened on my previous OS, Fedora Kinoite (Up to date version as of 10/15/2026)
  • Time of crash would be around 3 minutes semi-consistently, also happens when headset is idle with it's displays off.

Attachments
vrcompositor copy.txt
vrcompositor-linux copy.txt

MMarkosha2004 2026-10-17 github

Seems to be fixed with 2.18.4 on my end

Cancel that, this still persists with some titles, will update in a sec

MMarkosha2004 2026-10-17 github

So, as it is right now, the situation with this issue is that it sometimes occurs, sometimes not.

I'll include most of the crash dumps, though I am, at the same time, sure, as the devil himself, that these will repeat

Steam client build/version: 1792110651
SteamVR version: 2.18.4 beta
Linux distro: Nobara 44
Runtime diagnostics:

runtime diag.txt

Steam and SteamVR logs:

steam-logs.tar.gz

Minidumps:

steam-minidumps.tar.gz

Additional context:

Videos:

take 1: https://youtu.be/UGUWD4MeLCk
take 2: https://youtu.be/BKwUO64JyLo

Uploading 2 takes because I thought I messed up and had to re-record. After realizing that I won't be able to reproduce issues mentioned, it was decided that I need to upload two versions. Hopefully they both remain related to this issue

steamwebhelper dumps:

steamwebhelper 1.tar.gz

vrcompositor dumps:

vrcompositor 1.tar.gz

Edit: I should also add that all dumps are sorted by time they occurred. Format hh-mm

JJnnovation 2026-10-20 github

UPDATE

I got it working semi stable (with some minor unrelated issues). I went to the SteamVR config file and added these:

"camera" : {
"enableCamera" : false,
"enableCameraForRoomView" : false
},

It appears the issue is a stacking fault with the camera system that eventually passes some safety threshold that just kills it.

Of course this is just a band-aid solution but at least it allows you to play games until the devs find a fix.

Nothing extracted yet.