protonscr

Bellwright

protonopen appid 1812450Game compatibility - Unofficial
ValveSoftware/Proton#8270 · opened 2024-11-27 by Thaddeusz · updated 2026-03-30 · 8 comments · github · game page · search this game
1 matching comments, n / p to jump
TThaddeusz 2024-11-27 github

Compatibility Report

  • Name of the game with compatibility issues: Bellwright
  • Steam AppID of the game: 1812450

System Information

I confirm:

  • [X] that I haven't found an existing compatibility report for this game.
  • [X] that I have checked whether there are updates for my system available.

Symptoms

Unhandled Exception:                       
System.NullReferenceException: Object reference not set to an instance of an object
  at CrashReporterWindows.Program+<>c.<Main>b__0_0 (CrashReporterCommon.CrashReport+StackFrameReport t) [0x00006] in <d94e0640bed04438be7f54f15f423dae>:0 
  at System.Linq.Enumerable+WhereListIterator`1[TSource].GetCount (System.Boolean onlyIfCheap) [0x00018] in <a38d71b964e545c18a1583170be4fc6f>:0 
  at System.Linq.Enumerable.Count[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x00029] in <a38d71b964e545c18a1583170be4fc6f>:0 
  at CrashReporterWindows.Program.Main (System.String[] args) [0x000ce] in <d94e0640bed04438be7f54f15f423dae>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at CrashReporterWindows.Program+<>c.<Main>b__0_0 (CrashReporterCommon.CrashReport+StackFrameReport t) [0x00006] in <d94e0640bed04438be7f54f15f423dae>:0 
  at System.Linq.Enumerable+WhereListIterator`1[TSource].GetCount (System.Boolean onlyIfCheap) [0x00018] in <a38d71b964e545c18a1583170be4fc6f>:0 
  at System.Linq.Enumerable.Count[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x00029] in <a38d71b964e545c18a1583170be4fc6f>:0 
pid 322012 != 322011, skipping destruction (fork without exec?)

Reproduction

steam steam://run/1812450

TThaddeusz 2024-11-27 github

Runs with proton 7.zero-6, but in the menu it says cannot connect to steam and closes

Ppazembrz 2025-04-09 github

Compatibility Report

System Information

  • GPU: AMD RX 7900XTX
  • Video driver version: 25.0.2-2
  • Kernel version: 6.14.0-1-MANJARO
  • Proton version: All(stable, experimental and ProtonGE)

Symptoms

UPDATE:
Looks like the bug was in the game after all. The devs took another look at my issue and managed to fix it.

Loading the game saved on older game version in the newer version is causing the game to crash. According to the devs, on Windows game loads without any problem. Also according to the game devs the error is caused by Proton probably missing implementation of some functions, not by the game itself:
Image

Proton logs:
steam-1812450.log.zip

Game logs:
Bellwright.log.zip

Save game causing the crash:
Polo_0.sav.zip

Kkisak-valve maintainer 2025-10-24 github

Bellwright (1812450) - Memory/CPU leak during loading screen causes OOM kill

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9134.
@BillibuBergez posted on 2025-10-24T06:54:31:

Game: Bellwright (AppID 1812450)
Proton Version: Proton Experimental and Proton GE tested
OS: Ubuntu (latest)

ISSUE:
Game launches but during loading screen experiences massive memory and CPU leak. CPU spikes to 200%, RAM consumption grows progressively until system forces OOM kill. The Proton log shows thousands of unwind operations (C++ exception handling) consuming all resources.

SYSTEM SPECS:

  • CPU: 16-core AMD/Intel (showing 16 CPU threads)
  • GPU: NVIDIA GeForce RTX 2060 with driver 580.95.05
  • RAM: 16GB total

STEPS TO REPRODUCE:

  1. Launch Bellwright with any Proton version
  2. Observe loading screen
  3. Within 1-2 minutes, RAM consumption grows to 85%+
  4. CPU usage spikes to 200%
  5. Game freezes and gets OOM killed

PROTON LOG:
Shows extensive unwind operations indicating C++ exception handling loop.

LAUNCH OPTIONS TESTED:

  • _force_vk_vendor=-1 %command% -force-d3d11 -windowed
  • Various Proton versions and memory limiting attempts
  • All result in same memory leak behavior

ADDITIONAL NOTES:
Game works fine on Windows, issue is specific to Linux/Proton.

Ssimifor 2025-10-26 github

@BillibuBergez I didn't see a memory leak on my end checking on my desktop and laptop, but the game takes a lot of memory by the time the game starts (~11Gb on desktop and ~10GB on laptop), tried to check on windows 11 but something crashed during the loading screen and it didn't finish loading (though at that point it was already taking 7GB). However, I can see people on reddit surprised how the game can take around 12GB of memory, depending on how many programs you have open it might actually just be running out of ram the game is requesting, so it'd be interesting to know if reducing your ram usage to the minimum allows the game to start or if will still take all available memory anyway

BBillibuBergez 2025-10-27 github

@simifor I also tried limiting the app's RAM to 10-12 GB, but I kept getting the overconsumption notification. The game would either crash or sometimes even restart my whole session.

Were you able to launch it successfully? If so, what was your setup? A specific Proton version, or maybe a third-party tool alongside the standard ones?

Any help would be greatly appreciated!

Ssimifor 2025-10-27 github

@BillibuBergez didn't do anything special, could get in game and move my character, I didn't change any settings but things like lowering texture quality should help you at least get in game. Tried with both proton 9 and bleeding edge and both worked. How much ram is your system using before launching the game?

My desktop has 32GB of ram but my nvidia laptop has 16GB like is your case, though I'm a bit behind on driver, I'm currently on 580.82.09

BBillibuBergez 2025-10-27 github

@simifor I'll give it another shot. My plan is to set everything to low first, just to see if it even launches, and then adjust the settings based on performance. I'll try it with Proton 9 and no additional tweaks.

On a side note, after closing all apps and minimizing RAM usage, I'm seeing about 20% is already in use before even starting the game, which leaves roughly 10-12 GB of RAM free for other processes.

I'll try again anyway. Thanks! :)

Kkisak-valve maintainer 2026-03-30 github
Bellwright (1812450) - Crashes after 2-3 minutes with LowLevelTasks::FScheduler::CreateWorker EXCEPTION_ACCESS_VIOLATION - Memory budget exceeded

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9628.
@manfredsteger posted on 2026-03-30T05:05:46:

Compatibility Report

Name of the game: Bellwright
Steam AppID: 1812450

System Information
GPU NVIDIA GeForce RTX 4070 Ti (12GB VRAM)
Driver Version 595.58.03
CPU Intel Core i9-9900K
RAM 32 GB
OS Nobara Linux 43 / Bazzite (reproduced on both)
Kernel 6.19.10-201.nobara.fc43.x86_64
Filesystem btrfs

Proton versions tested (all crash)

  • GE-Proton10-34
  • Proton Experimental
  • Proton Hotfix
  • Proton 9.0

Launch options tested (all crash)

  • No launch options
  • force_vk_vendor=-1 DXVK_ASYNC=1 gamemoderun %command%
  • WINE_LARGE_ADDRESS_AWARE=1 %command%
  • WINE_SIMULATE_WRITECOPY=1 %command%
  • WINE_SIMULATE_WRITECOPY=1 PROTON_DISABLE_KERNEL_WRITEWATCH=1 %command%
  • ulimit -n 524288 && %command%
  • %command% -threads=8
  • %command% -gc.TimeBetweenPurgingPendingKillObjects=120

Issue description

Game launches and runs for approximately 2-3 minutes before crashing with EXCEPTION_ACCESS_VIOLATION in a background/foreground worker thread. Crash is 100% reproducible regardless of Proton version, launch options, or fresh prefix.

Important observation: The lower the graphics settings, the longer the game runs before crashing. At lowest settings the game runs noticeably longer. This strongly suggests a memory/VRAM budget issue under Proton.

Previously worked: Game ran for 200+ hours on Bazzite with an older kernel without any issues and no special launch options required.

Critical log entries — Crash 1 (Background Worker)

[2026.03.28-09.39.54:588]LogMutableCore: Failed to keep memory budget. Budget: 5120, Current: 8713, New: 1450
[2026.03.28-09.39.54:598]LogMutableCore: Failed to keep memory budget. Budget: 5120, Current: 8704, New: 1565
[2026.03.28-09.40.02:495]LogWindows: Warning: Failed to retrieve TPM device information
[2026.03.28-09.40.02:495]LogWindows: Warning: Failed to retrieve secure boot information
[2026.03.28-09.40.02:495]LogThreadingWindows: Error: Runnable thread Background Worker #8 crashed.
[2026.03.28-09.40.02:495]LogWindows: Error: Fatal error!
[2026.03.28-09.40.02:495]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000021447be0ba
[2026.03.28-09.40.02:496]LogWindows: Error: [Callstack] LowLevelTasks::FScheduler::CreateWorker'::'2'::<lambda_1>::operator()()
[2026.03.28-09.40.02:496]LogWindows: Error: Crash in runnable thread Background Worker #8
[2026.03.28-09.40.02:502]LogExit: Executing StaticShutdownAfterError
[2026.03.28-09.40.02:510]LogCore: Engine exit requested (reason: Win RequestExit)

Critical log entries — Crash 2 (Foreground Worker)

[2026.03.28-17.46.33:034]LogThreadingWindows: Error: Runnable thread Foreground Worker #1 crashed.
[2026.03.28-17.46.33:034]LogWindows: Error: Fatal error!
[2026.03.28-17.46.33:035]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION
[2026.03.28-17.46.33:035]LogWindows: Error: [Callstack] LowLevelTasks::FScheduler::CreateWorker'::'2'::<lambda_1>::operator()()
[2026.03.28-17.46.33:035]LogWindows: Error: Crash in runnable thread Foreground Worker #1
[2026.03.28-17.46.33:045]LogExit: Executing StaticShutdownAfterError
[2026.03.28-17.46.33:053]LogCore: Engine exit requested (reason: Win RequestExit)

Network errors preceding crash

LogNet: Warning: UActorChannel::ProcessBunch: ReadContentBlockPayload failed to find/create object. RepObj: NULL, Channel: 110
LogNet: Warning: UActorChannel::ProcessBunch: ReadContentBlockPayload failed to find/create object. RepObj: NULL, Channel: 133

Secondary error (separate session)

Pure virtual function being called while application was running (GIsRunning == 1)

Root cause hypothesis

  1. Proton fails to correctly emulate the Windows memory management that UE5 uses for the Mutable character system (LogMutableCore)
  2. TPM/Secure Boot check under Proton triggers undefined behavior in background worker threads
  3. The combination causes LowLevelTasks::FScheduler to access invalid memory

Workaround attempts that failed

  • Fresh Proton prefix
  • All Proton versions tested
  • Lowering graphics settings extends runtime but does not prevent crash
  • Creating 16GB swapfile + disabling ZRAM (ProtonDB suggestion) — not fully testable due to btrfs filesystem constraints

Related issues

ProtonDB reference

https://www.protondb.com/app/1812450

Proton versions

Launch options

Launch lines

Upstream links