RPG Maker MV's Memory Leak problem

[Crysillion]

I know there's a board for posting bug reports, but I cannot for the life of me find it. Sorry if this is the wrong place!


I recently made a post highlighting RPG Maker MV's memory leak problem, which can be found here: http://infinitelegacyrpg.tumblr.com/search/memoryleak

I'm throwing it out there because I'm hoping that, with more information, we can eventually finally solve this problem for good.


This memory leak problem also happens with plugins such as TDDP's Bind Pictures to Map plugin. Over-all, the issue seems to involve anything that places images onto the maps. I spoke with Yanfly here: https://www.*******.com/Yanfly/community (question at the top by Crysillion, sorry I can't seem to figure out how to link to the question directly, but at the time of this posting it's at the top of the page because it's the newest, so it shouldn't be hard to find). The conclusion was drawn that this is an issue with RPG Maker MV itself. I am inclined to agree.


Just wondering what the consensus is on this one.

 

[Andar]

The last remaining memory leak in the engine itself is already solved - the solution will be in one of the next patches. You can also find it in one of the topics about it here on the forum if you don't want to wait for that patch.


However, the memory leaks in plugins cannot be solved in any way by Degica, they need to be solved by the plugin writers as patches to the plugins.


No way around that, because memory leaks are NOT coding bugs, they are logic bugs in the memory management of whatever memory use of the engine or plugins.


And the engine cannot solve memory management for plugins, that needs to be handled by the plugin itself.


And yes, for a lot of plugins that most probably will not happen simply because a lot of hobby-programmers don't know enough about memory logik to handle that correctly.

 

[Crysillion]

The last remaining memory leak in the engine itself is already solved - the solution will be in one of the next patches. You can also find it in one of the topics about it here on the forum if you don't want to wait for that patch.


However, the memory leaks in plugins cannot be solved in any way by Degica, they need to be solved by the plugin writers as patches to the plugins.


No way around that, because memory leaks are NOT coding bugs, they are logic bugs in the memory management of whatever memory use of the engine or plugins.


And the engine cannot solve memory management for plugins, that needs to be handled by the plugin itself.


And yes, for a lot of plugins that most probably will not happen simply because a lot of hobby-programmers don't know enough about memory logik to handle that correctly.

As I am using Steam, I believe I will have no choice but to wait.


If there's a way to apply this patch even though I'm using Steam, please let me know. As well, I would appreciate it if you could show me where this patch is, as I'm not sure where that kind of thing gets posted. Thanks!

 

[Andar]

The patch goes into the project, not into the editor - and projects are never updated automatically, neither steam nor standalone.


And I don't have the link - I only know that it was an answer given about one or two months ago in one of the topics about memory leaks.

 

[lawina]

The patch goes into the project, not into the editor - and projects are never updated automatically, neither steam nor standalone.


And I don't have the link - I only know that it was an answer given about one or two months ago in one of the topics about memory leaks.

This one?

 

[Crysillion]

This one?

Works wonderfully! Thanks!

 

[Andar]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.