I had some cheaters create over 5,000 GameINI's somehow, so props to them, but I've since cleaned this (I spoke about this on Discord with you) and ever since those 5,000 GameINI's were created, all the BDB's seems to be unusable and spit out these Out of Memory errors.
It can't be anything in my code because I released an update around a week ago (everything was working normally) and then a day later I woke up to the 5,000 INI's and the Out of Memory errors on all worlds (BDB's). I'll double check through the code but I doubt it would be anything code related as I try to keep performance above 60fps at all times.
Sending variable image_angle = 0 Sending variable image_blend = 16777215 Received Lock for BDB 1 Received BDB 1 Loaded world data with index: 1 Out of Memory allocating 28988283676819472 bytes Compile finished: 16:16:58
Here's where the errors happen (Happens in all BDB's ids) after the 5,000 GameINI's were created.
This isn't a code issue as the update that I released was perfectly fine, and loaded everything in less than a second. After the 5,000 GameINI's were created, then the error started happening on every single older client using BDB's, and the update that was working fine before the 5,000 GameINI's were created.
I will add a breakpoint and get back to you. Could this be a GameINI cache issue? It's trying to allocate around 20 petabytes of data, which is ridiculous.
OK, so it seems to crash with the Out of Memory error before it even tries to load the BDB, but that doesn't make sense because it's running code in on_load_world before it crashes, but it doesn't even seem to reach that script before crashing.
Would it just be easier to maybe move the entire game data (on your end) to a new GameID, maybe this would fix the issue? We would most likely have to talk on Discord about this though.
When I comment out the ds_grid_resize, I get thousands of these in the console very quickly:
Grid 1, index out of bounds writing [0,4253] - size is [32,32] Grid 1, index out of bounds writing [0,4253] - size is [32,32] world_set 2 OK 4 world set Grid 2, index out of bounds writing [0,4253] - size is [32,32] Grid 2, index out of bounds writing [0,4253] - size is [32,32] gms_bdb_read OK Grid 0, index out of bounds writing [0,4254] - size is [32,32] Grid 0, index out of bounds writing [0,4254] - size is [32,32] world_set 1 OK Grid 1, index out of bounds writing [0,4254] - size is [32,32] Grid 1, index out of bounds writing [0,4254] - size is [32,32] world_set 2 OK 4 world set Grid 2, index out of bounds writing [0,4254] - size is [32,32] Grid 2, index out of bounds writing [0,4254] - size is [32,32] gms_bdb_read OK Grid 0, index out of bounds writing [0,4255] - size is [32,32] Grid 0, index out of bounds writing [0,4255] - size is [32,32] world_set 1 OK
I've never touched them and they were working before the cheaters created the INI's. I think it might've downloaded the INI data on all clients and then never really got rid of it, so maybe some sort of caching issue with my game that only you could fix.
Maybe we should try moving my game to a new GameID, I don't know if you could do that or not but maybe it's worth a shot?
Your ongoing help is appreciated nonetheless. But this is definitely an issue your side and I have no idea on how either me or you are to do to even try and fix this. I guess you need more information about what happened to maybe fix it.
You could try moving to a new GameID, but I won't be able to move any of your current INI data or other stored data to a new GameID. I can either restore backups from another, earlier, date, or I can delete all BDBs for you.
OK, everything seems to be back to normal and the width and height values are back to what they should be (32, instead of the 15000+), not sure if you did anything to fix this, but it's all working perfectly again. Thank you for your ongoing support as always.
Might be an issue with the BDB system alltogether then. It seems like quite a few people have been having weird issues with them lately. It's difficult to figure out what the issue is though because we can't really provide debug information.
But yes, in my case the height and width values were over 15000+ when they should be 32, but it seems to have fixed itself without me doing anything, which is what makes giving you information to find out what was wrong: tricky.
I presume those height and width values are incorrect, so let's try deleting the BDBs altogether, and if that doesn't work then I will move to a new GameID, but would you be able to move my upgrades to the new GameID?
To add on, if this is a flaw in your system (which I'm almost if not 100 percent certain it is), this can be and will most likely be done to me again as an attack, so maybe we should arrange a time and speak on Discord for an hour or two to discuss what happened.