Memory leak?

[NotGodsArmy666]

OK, to begin with. I haven't started to trace the bug yet, I just want to confirm if I am the only one or not.

 

I use MMC 5 to install all mods and handle different instances of MC.

 

I have in MMC set Java up to use up to 768 MB.

 

If I play MC 1.7.2 with any 1.7.2 (any I tried, starting back at some late 900er) forge version and Optifine 1.7.2 HD (no other mod installed at that point) after some time (usually several hours) I recognize that my free ram has significant dropped until it is running out at some point. (which results in a very laggy game play and very low frame rate)

 

So I dunno yet if its caused by minecraft, by optifine, by forge, or by MMC 5.

 

Is it a known bug?

 

If it is: Is there a workaround (other than restart MC)?

 

And why the heck are the forum formatting buttons are currently not working for me? (probably some wired settings in my browser .. which is set up to be so secure it doesn't display any website anymore ;p )

[LexManos]

Memory leaks, if they exist are rather hard to find.

Unless you have a consistant way to reproduce or you know how to debug it yourself we can't help you much.

However, I can say for certian we can not take your report if it involves other mods as there is no way for us to know if it's us or the other mod that would be causing it.

So if you find a way to reliably reproduce {like and action in game that significantly eats ram} and it happens with NO other mods. Then we can take a further look.

[Nuiofrd]

The FTB Team said there is a vanilla bug that caused a memory leak every time you enter a different dimensions.

[sequituri]

java, since it has a reasonable garbage collector, normally doesn't suffer much from memory leaks. However, bugs in code that create circular reference dependencies most certain can create such problems. For example: when you do "new Thing1(new BigObject(args))," then normally, minecraft sees when the inner object goes out of scope and frees the memory.

It is possible, though, to store the reference where it never goes out of scope, and keep doing it with more and more. That would gobble memory horribly. IT IS NOT A LEAK. It has simply never gone out of scope. The game still has references to this memory left laying around. If it happens with dimension travel, that might be a good place to nail it down to.

A good place to check is the mojang bug tracker.

[LexManos]

You do realize that thats exactly what causes memory leaks.

Holding references where you shouldn't thus causing the GC to not collect the memory is exactly what a memory leak is.

However, it's fairly hard to debug, unless you have a way to reproduce it.

[fabricator77]

The FTB Team said there is a vanilla bug that caused a memory leak every time you enter a different dimensions.

 

I did ask if they had any more details on this, no reply.

 

Most likely it's the Teleporter class, as that creates (and presumably hangs onto) a number of things like two WorldServers.

Could also be a lot of different things in the world itself, like chunk loading/unloading.

[sequituri]

Really, LexManos.

 

Memory "Leaks" were the hallmark of C and C++ programming. As it's very easy to say alloc() or new() and then just reuse the point later for something else. Since the memory is not free nor is it accessible at any point with any option to reclaimed it, it has leaked. It the java world, memory cannot "leak" the same way. The memory is always accessible unless the user has dome something very unjava-like. Like create an object with a reference to itself. Although, there are garbage collectors that can even detect that and free the lot.

[luacs1998]

Generally.. I'd say..  Don't dispute Lex's reasoning, you're usually rewarded with a ban for your efforts

 

Anyways, before accusing Forge of performance issues/memory leaks/all those crud, the accepted way is to come to us with a profiler report or something.

[LexManos]

Memory "Leaks" were the hallmark of C and C++ programming. As it's very easy to say alloc() or new() and then just reuse the point later for something else. Since the memory is not free nor is it accessible at any point with any option to reclaimed it, it has leaked. It the java world, memory cannot "leak" the same way. The memory is always accessible unless the user has dome something very unjava-like. Like create an object with a reference to itself. Although, there are garbage collectors that can even detect that and free the lot.

Please don't try to sound smart. It just makes you sound annoying.

A memory leak is when memory leaks, FOR ANY REASON. If memory *should* of been freed and it hasn't then it has leaked.

Does it have to be explicitly that the programmer did not call free() or that the GC has broken? No, it's just shit is staying around behind it's intended end of life.

Who decides when the memory's EOL is? The programmer, not the program.

So ya, stop being an ass 'Lol java has the garbage collection so its impossible to "leak" memory lolololololol' <~~What you sound like.