🐈 in other news i'm stress testing the password system by making sure all 85 million ish passwords decode correctly without inconsistencies and the game maker runner keeps running out of memory every 12 mlllion or so, claiming to have hit a peak 48 GB of memory before crashing (i don't think i have that much RAM???)
@lovegame right before it hits 48 gigabytes, if you look in windows explorer or whatever, do you find a bunch of your hard drive space is suddenly missing?
I think that if your process is gradually using all the memory like this while running a single loop, this probably means you have a memory leak. Would it be helpful if I tried to give some advice about this?
@mcc i'm using game maker, which is mostly garbage-collected these days (and i'm not using any feature that isn't garbage-collected) so i think it might be difficult to figure out the source of the leak.... it could be a bug in their gc, or it could be that i wrote my loop in a way that doesn't let things get collected? i'm not sure if my password generation/validation still leaks memory in normal circumstances or if it gets cleaned up
@mcc oh, i think i figured out the problem - the garbage collector in game maker only runs at the end of a frame (even if you call the "gc_collect" function, that just tells it to run at the end of the current frame) and my loop is happening within one frame
i asked my friend Miguel Spookysquid who uses a lot of gamemaker and he said there are some types of deallocation that only occur manually or when you change rooms. but it sounds like you're familiar with that. he also said the debugger ought to be able to show you what's in scope, so you could just look in there and see if you see anything huge. But that won't help if the GC is being deferred…!
@lovegame in non-gamemaker world the standard advice here is to double check if you're accidentally retained a reference to something, like adding something to a list or dictionary and forgetting to remove it. and that would be what the debugger would help you with, but it sounds like you've found the actual problem!
Add comment