Lemma Soft Forums

Due to a post in a demo thread for my dungeon crawler I'm currently trying to find out where some unexpected memory usage could come from. Due to my (bad) experiences with garbage collection in other languages I'm wondering if that could be the cause here (the documentation I found about python garbage collection doesn't tell me how good / efficient it is or how often it is normally run ).

So basically what I'm doing is this

1.) I'm loading images from the disk during initialization
2.) Ingame I'm showing the same image at different locations on screen under different tags (but at the beginning I'm using renpy.scene() before beginnign to draw the images)
3.) I'm waiting until the user cliks on an image button (on a screen) or presses a specific key until I go back to 2.)

I'm NOT using gc.collect or anything.

Seemingly the memory allocation varies quite greatly so the question is can point 2 be the cause for it so that point 2 is triggered multiple times without the memory used in between beeing freed again? (thus using up more and more memory instead of about the same amount?)

On my machine, your demo starts at ~720MB internal memory and eventually stabilizes at ~900MB. There are no noticeable garbage collection pauses. In fact, it doesn't seem like any images ever get unloaded.

the enver get unloaded makes sense in a way as all images are pre loaded but the increase by 180 MB DURING play is something I'm not getting. do you have any idea there? (like I said the way I do things is just those 3 points above)

If you're using renpy.cache_pin, I suggest you better not to use it as possible as you can. In my experience, it likely causes memory issue.
One more advice is use Transform a lot. For example, right side of the screen should be shown with Transform("left_side_image", xzoom=-1), so memory usage will be half. Using smaller textures with Transform zoom is another idea.

never used renpy.cache_pin . what is that?
will look into the transformations there (maybe I can save loading both right and left side there [need to look how it impacts performance if I do that on the fly]) tnx

Wolf wrote:never used renpy.cache_pin . what is that?

It's a function to load images permanently over config.cache_size. This should be used on only UI images.

the enver get unloaded makes sense in a way as all images are pre loaded but the increase by 180 MB DURING play is something I'm not getting. do you have any idea there? (like I said the way I do things is just those 3 points above)

Ren'py records many data for rollback and some others. It's better to keep at least 200mb free RAM space for it in a complicated program.

Hmm interesting. The game uses 528-576 MB for me. when I put up gc.collect() at the end of each rendering that is reduced to 430-491 MB