Do you actually think that's a memory leak? You blew up a million TNT.
I have news: Doing things on a computer uses memory. Another piece of news, memory leaks are when a program slowly takes up more memory when idle. Not when you're doing something that is very memory intensive, like blowing up an entire terrain of TNT.
Uh, Minecraft isn't really applicable to "memory leaks" (technically it is and can memory leak but for simplicity we're going to say it's not and shut up). It has a set maximum addressable memory size, generally speaking it'll never really approach this if it DOES approach it, it'll crash and just well, cease to exist.
Other programs generally don't have a maximum addressable memory size and will happily consume more and more memory until all 2/3/4GB of addressable memory is consumed. Then epically blow up your computer.
If you detonated all that TNT, within 1-2 seconds of the first TNT asploding. Minecraft will reach it's addressable memory limit and die. The reason behind this is, each entity is an object, and an object contains an assortment of variables, each variable takes up memory and the more objects means the more variables meaning the more memory required. You can't dispose of these variables whilst the object is in use or things will just magically start disappearing and break the game (interesting examples of crazy **** which can happen when you exceed recommended numbers of objects is when people intentionally overload games, this was really easy to do on Halo Co-op, you just respawned and killed player 2 over and over (their weapons, objects, dropped and you ended up with like 10000000 of plasma pistols and AI and effects and all sorts of **** just failed).
All you've done is overloaded Minecraft like the primitive ape you are and blamed Minecraft.
Edit: On the subject of above, isn't TNT also a TileEntity, therefore has additional variables? So it's still an object...
I've had the game paused and it's reached over 930,000 k of memory. It's not a bad computer, it's not loading the map with 10 billion tnt blocks, it's not a huge map file. Even now, memory steadily increasing while the game is paused. I don't think it's a leak, since Minecraft has always been a memory hog. It's just java being a piece of ****.
For people who think the memory usage has something to do with all that :tnt:*, you are bad at computer.
Minecraft is designed to have a certain amount of memory allocated to it, and should never -- under any circumstances -- overstep those bounds unless there is a memory deallocation error, or 'leak'. In fact, the design of Minecraft is such that every block has a certain static amount of data associated with it which is supposed to prevent this kind of tomfoolery.
Unless TNT has some special memory cases external to being a block and after the TNT was gone the memory usage went back to normal, that there's a leak.
*I should clarify, this is unexploded TNT we're talking about.
OK, to clarify a few things. I was sitting at about 750,000K usage BEFORE the detonation. AFTER detonation I reached this number. It kept going higher, MineCraft DIDN'T crash. It stopped making sounds and updating **** at about 1,500,000K usage. The reason it doesn't look detonated is because its a Windows Aero preview, and MC was minimized for the picture. After letting MC sit a while, it does manage to top 1,000,000K usage on its own, normal terrain and the like. So it seems MC does have a memory leak somehow. Maybe not directly, but probably cause Java sucks at that sort of thing. I'm hoping it gets sorted out quickly. I also wouldn't mind multi-core support, as MC maxes at 50% CPU usage on my quad-core.
Rollback Post to RevisionRollBack
Quote from Corvak »
Yo dawg, I heard you like minecrafts, so I put a minecraft in your minecraft so you can minecraft while you minecraft.... You know, its just a saying but this guy could probably DO it.