Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Nivim]

 I am not sure how much of a bug this is, or if it simply wasn't done. But Dwarf Fortress does not close cleanly, it slows down the computer afterwards and causes minor interference with other programs. I am guessing either Toady was too lazy to go through the trouble of programming a clean exit, or he is waiting for when the game is at version 1.0 so he wont have to mess with it too much.

[ToonyMan]

What do you mean?  I don't experience any problems with shutting down DF.

[Sowelu]

Are you using a non-Windows version?  The Windows version works just fine for me, but maybe the Mac version leaves cruft lying around due to inexperience with that platform, say.

[Derakon]

I'm on a Mac and I've not noticed any problems post-shutdown. To my knowledge, it shouldn't be possible to continue using resources after program exit unless you've made child processes and then not forced them to exit; Dwarf Fortress doesn't make child processes, so it can't leave effects behind after it's done.

Perhaps you're noticing a temporary slowdown as the memory Dwarf Fortress was using is freed and other programs start paging stuff in from the disk? How long does your slowdown last? And please tell us what operating system you're using and your computer specs.

[Nivim]

 It's the same effect most programs in existence have and goes away when you restart the computer. It isn't that much, around 5 fps hit for most things. A common problem, and it isn't specific to an operating system or computer setup (it's a Windows XP with run-of-the-mill decent processor and graphics card anyway). I was just pointing it out and to ensure that Toady would take care of it at some point.

[Keiseth]

I honestly have no idea what you speak of. I've started and closed DF hundreds of times while working on modded races and I have felt no ill effects- and my computer is slow enough that even the smallest decrease in efficiency would be instantly noticeable.

I was thinking you were referring to some sort of memory leak, but that would be resolved when the process ended (as I've made a huge memory leak before and it was gone by simply closing the program for good.)

Might it be a problem specifically with your computer or operating system?

[eerr]

Is it version 40d11?
I believe that one might be double-threaded now.

[Sowelu]

It's the same effect most programs in existence have and goes away when you restart the computer. It isn't that much, around 5 fps hit for most things. A common problem, and it isn't specific to an operating system or computer setup (it's a Windows XP with run-of-the-mill decent processor and graphics card anyway). I was just pointing it out and to ensure that Toady would take care of it at some point.

I also have no idea what you're talking about.  And no offense but if you say "most programs" have this problem, you're wrong.  This sounds like something wrong with your computer.  Maybe you've got very low RAM, and you're actually seeing paging issues?

[Corona688]

Not many programs churn through memory the way DF does.  Lots of things consume lots of memory, but DF actually uses most of what it has fairly often.  I wonder if its memory fragmentation...  Not much else would cause nonspecific performance issues after a program quits.  Except paging, and if it was that, I'm pretty sure you'd know :p

[Jay]

I am guessing either Toady was too lazy to go through the trouble of programming a clean exit, or he is waiting for when the game is at version 1.0 so he wont have to mess with it too much.

No.
Toady's exit code is fine.
There's a couple of reasons this could be:
If you did any memory editing and/or it crashes, it might not close cleanly.
Check for the process still running after exit.

Memory fragmentation - Free bits in the memory in non-sequential areas are taken by the same program.
Very similar to fragmentation of hard drives, but resolved by a simple restart, as RAM clears when it loses power.

If "most programs in existence" cause it, it's clearly not exclusive to DF, and it's clearly not a DF bug.

[Blacken]

Is it version 40d11?
I believe that one might be double-threaded now.

All threads die on process exit. That's kind of the point of threads: to not go outside the process space.

[Dant]

if ur on windows theres a flag on the registry that u have to set otherwise windows wont unload the dlls the program required

hkey_local_machine->software->microsoft->windows->explorer, if it doesnt have a AlwaysUnloadDll key create it and set the standard value to 1

thats an old windows trick but most ppl never heard of it

[Jay]

if ur on windows theres a flag on the registry that u have to set otherwise windows wont unload the dlls the program required

hkey_local_machine->software->microsoft->windows->explorer, if it doesnt have a AlwaysUnloadDll key create it and set the standard value to 1

thats an old windows trick but most ppl never heard of it

That key is moot with Vista/7, as it automatically unloads unused DLLs.
Perfectly valid with XP or lower.

However, the number of DLLs that DF loads is not even close to capable of causing a 5 FPS drop in anything.
I see roughly 5MB of DLLs.  If losing 5MB of RAM is causing a 5 FPS drop, I think you need more RAM.

[LegoLord]

if ur on windows theres a flag on the registry that u have to set otherwise windows wont unload the dlls the program required

Please spell out the words.  "ur" just sounds clumsy in my head.

Anyway, DF is not and never will be double-threaded.  I'm fairly certain Toady said this himself.  I'm given to understand he would have to rework the program quite extensively for that to work.  Even so, I am 100% positive that 40d11 isn't double threaded.  So it's not even possible for it to be a problem with double-threading.  My guess is just poor RAM.  DF doesn't cause problems for me when closing, and I have RAM on my computer that is really in need of upgrading.

[SHAD0Wdump]

I wonder if its memory fragmentation...

I think I remember hearing somewhere else on this site about that,someone said that DF fragments horridly.

I have no experience with programming,I'm just telling you what I remember sounded bad.