View Issue Details

IDProjectCategoryView StatusLast Update
0013385Dwarf FortressTechnical -- Generalpublic2026-01-06 07:26
ReporterBurningAmber Assigned To 
PriorityhighSeveritycrashReproducibilityalways
Status newResolutionopen 
PlatformSteamOSNobara (Fedora)OS Version43
Product Version53.08 
Summary0013385: Constant memory increase until crash
DescriptionAfter launching the game, system monitor reports a constant memory increase from dwarf fortress. After an hour of usage, stock DF is using over 20gb of memory, and will continue to use more until the OOM Killer runs. This appears to get worse with DFHack enabled.

The memory usage is visible only staying on the title screen, and gets much, much worse after loading a fort. after quitting the fort back to the main menu, memory usage does not decrease. The program must be closed before memory usage drops to normal, if i want to avoid a crash.
Steps To ReproduceOpen the game, and wait. intensifies after loading a save.
Additional Informationpossibly related bug tracker post: https://dwarffortressbugtracker.com/view.php?id=13378
DFHack Issue Tracker post: https://github.com/DFHack/dfhack/issues/5689
Tagslinux, memory, SIGABRT

Activities

rannon

2026-01-02 11:03

reporter   ~0043079

I can reproduce this issue. I tried forcing the legacy 1.0 linux Runtime in Steam and that did not solve the problem. However, if I force the windows build of DF with Proton Experimental, then the issue is resolved. In that scenario, I think Proton is using the linux Runtime 3.0 so, I suspect that the linux build of DF needs to be compiled/built against a newer version of the Steam Runtime. See the github for details: https://github.com/ValveSoftware/steam-runtime

I could be wrong about the root cause but, that's my best guess. Please note that my save file is in the Linux build and I cannot access it when I switch over to the windows build with Proton so, I'm stuck playing for like 45 minute stretches until my RAM fills up.

mattvt3

2026-01-03 11:43

reporter   ~0043081

I can reproduce this on Arch linux as well. Changing the PRINT_MODE to 2D does not help.

RiverOmega

2026-01-06 07:26

reporter   ~0043091

I can reproduce the same issue running CachyOS (arch-based) with the native Linux version.

Workaround: switching to proton at the cost of FPS and a not so smooth migration of save files.

Add Note

Note

Issue History

Date Modified Username Field Change
2025-12-19 14:53 BurningAmber New Issue
2025-12-19 14:53 BurningAmber Tag Attached: linux
2025-12-19 14:53 BurningAmber Tag Attached: memory
2025-12-19 14:53 BurningAmber Tag Attached: SIGABRT
2026-01-02 11:03 rannon Note Added: 0043079
2026-01-03 11:43 mattvt3 Note Added: 0043081
2026-01-06 07:26 RiverOmega Note Added: 0043091