A leak is when the memory footprint gets bigger and bigger the longer the program is running.īut I do think some of is mods could easily have a leak. It's just inefficient usage, which is different from a leak.Ī leak not just "it could be designed to use less memory". It would only change how *long* it would take for the leak to break things, not *whether* it would do so. That's why it crashes, it's usage of mods is the most inefficient i've ever come across and the loading times are ridiculously slow A memory leak is not fixed by making code 64-bit.Ĭhanging the max cap of memory doesn't change whether there's a memory leak, nor change whether or not a memory leak is a problem. Not load everything into memory all in one hit regardless of whether it's being used or not then execute the program code on top.
A 64bit version would make efficient use of system resources when it needs to use mods and relinquish redundant memory usage when it isn't needed. Originally posted by ShadowPhoen1x:it's a memory leakage problem in the 32bit version, that's why it peaks everytime you use it.
0 kommentar(er)
