Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010619Dwarf FortressDwarf Mode -- Idle Behaviorpublic2018-03-13 06:192018-03-13 10:14
Assigned Tolethosor 
PlatformQNAP storage Unit hybrid stationOSLinuxOS Versionubuntu_1604
Product Version0.44.06 
Target VersionFixed in Version 
Summary0010619: Game Freeze with 100% cpu usage since update to 44.06
DescriptionGame was started with version 44.02, upgraded to 44.03, then 44.05 and 44.06.
The game freeze since 44.06 while in the main screen just letting the little dwarves go.

Currently under siege

Things are all running smoothly (bridge gates are sealing the fortress)
But game freeze after 5 minutes after loading this save.
(I saved up to a point where it freeze close to the loading point for easier review)
Steps To ReproduceJust load the game, and let it run.
It will freeze withing 1 game day.
check DF CPU usage.
Additional InformationSave available at this link: [^]
TagsCPU, freeze, freezing, ininite loop
Attached Files

- Relationships
duplicate of 0010615resolvedToady One Game freezes after some time - new 0.44.06 optimizations? 

-  Notes
ArmokGoB (reporter)
2018-03-13 07:13

Is this still happening in 44.07?
lethosor (manager)
2018-03-13 08:01

Can't reproduce this in 0.44.06 (OS X). It runs from 3/20/1324 to 3/24/1324 without issues. Note that on 3/21 it drops down to 0-1 FPS and stays there for a few minutes. Have you tried leaving it alone for a few minutes to see what happens?

Also, your save is one of the largest I've ever seen, and took several minutes for DF to load. I don't believe Toady has access to a very high-end machine either, so if you could try to get a smaller save to produce the issue, that might help.

Also, how did you download DF? Particularly, did you download it from a package manager? Those sometimes include a modified version of libgraphics, which is about the only Linux-specific thing I can think of (besides OS issues) that could cause a freeze at low FPS.
life-saver (reporter)
2018-03-13 08:18
edited on: 2018-03-13 08:58

Hi, I didn't try 44.07 yet, i can do it this noon (EST), and report back.
The save is big because I generated a 1300 years world.

It's not running on a high end machine. As mentionned, it's this thing. (I like it because it's like a server, and very stable) [^]

The low FPS you got is probably the trigger of the loop.
When it does on my side, the FPS still displays its usual 6 fps, and nothing is blinking on screen.(first occurence of the issue ran frozen for almost an hour before I noticed.

My DF installation is completely vanilla. Got the install from the official site.

I copied my init.txt and d_init.txt from my previous version.
(modified for no intro, no sound and show FPS I think.)
Do they change from 1 version to another? (I have backups of the originals. )I can also try to replace them by the original.

life-saver (reporter)
2018-03-13 08:19
edited on: 2018-03-13 08:35

*Same issue as [^]
and mentionned on reddit: [^]

Also in: [^] (comment below)

Ok, it's official (in my case) The linux version of DF 0.44.06 falls in an infinite loop. I'm running a fort since a few months, I'm running it since 44.02 And since the 44.06 update, it randomly falls in an infinite loop after a while. Since I run full screen, I was unable to get back to my UI, and had to restart the station. It did this many times, but last time I ran it in a window instead of full screen, so I was able to access my desktop, and open htop, and take a screen shot: [^] 4cores, 1 is 100% by DF

Game frozen, nothing blinks on screen (when some tiles should) No activity, no response, it's frozen.
Looking at htop, one of my cores is 100%, and DF takes 25% cpu. makes sense... so infinite loop...

EDIT: ok. screenshot strangely doesn't show 1 cpu 100%, but it was for a long time until I took the screenshot. It went back to 100% after. DF displays 100% cpu still.

lethosor (manager)
2018-03-13 10:13

This seems to be the same as 0010615, so I'm resolving it as a duplicate. Thanks for the useful information, though. I'll link to this report from there too.

- Issue History
Date Modified Username Field Change
2018-03-13 06:19 life-saver New Issue
2018-03-13 06:20 life-saver Tag Attached: freeze
2018-03-13 06:20 life-saver Tag Attached: freezing
2018-03-13 06:20 life-saver Tag Attached: ininite loop
2018-03-13 06:21 life-saver Tag Attached: CPU
2018-03-13 07:13 ArmokGoB Note Added: 0037908
2018-03-13 08:01 lethosor Note Added: 0037910
2018-03-13 08:01 lethosor Assigned To => lethosor
2018-03-13 08:01 lethosor Status new => needs feedback
2018-03-13 08:18 life-saver Note Added: 0037911
2018-03-13 08:18 life-saver Status needs feedback => assigned
2018-03-13 08:19 life-saver Note Added: 0037912
2018-03-13 08:28 life-saver Note Edited: 0037911 View Revisions
2018-03-13 08:29 life-saver Note Edited: 0037912 View Revisions
2018-03-13 08:34 life-saver Note Edited: 0037912 View Revisions
2018-03-13 08:35 life-saver Note Edited: 0037912 View Revisions
2018-03-13 08:58 life-saver Note Edited: 0037911 View Revisions
2018-03-13 10:13 lethosor Note Added: 0037914
2018-03-13 10:14 lethosor Relationship added duplicate of 0010615
2018-03-13 10:14 lethosor Status assigned => resolved
2018-03-13 10:14 lethosor Resolution open => duplicate

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker