- Line #952 tells us:
- But line # tells us:
- 17:33:39 [SEVERE] [ForgeModLoader] The world 9a93359 (btg1) has leaked.
That is... Odd.....
Let me think about this for a bit?
I am using FTB DW20 5.2.0 and I followed your instructions for version 1 to get rid of leaking memory.
It is rather odd. During testing I got the same error you did.
-- My testing history --
I should have checked the forums first, but decided to debug myself. I eventually found that CBE's version of wireless redstone was not gracefully unloading the Redstone Ether and was keeping it loaded in memory even after the world had been closed. I discovered this while trying to find a good world for my server. After 30 worlds my forge log was reporting around 34 worlds leaking and java was taking up 5g of system memory (normally 2g on my system). I also noticed that I could not delete worlds that I had just created and wanted to get rid of. The log reports showed that the redstone ether dimension was still in use. This issue ceased when I removed the CBE wireless redstone mods (granted, it may have been another mod interaction, but I could not find any other installed mod that uses the redstone ether).
After disabling CBE-wirelessredstone I found that the redstone ether was no longer persisting (obviously) and I could now delete old worlds, however, a memory leak still existed for consecutively created worlds. It is an odd issue and many people probably do not even notice that it exists, because unless you are looking for it and creating multiple worlds then you won't find it (these are not myst dimensions). The first world has no memory leak, but follow-up worlds report the last world as leaking memory. (I seem to remember reading that this may just be a forge reporting thing and not really be a memory leak, something to do with the way worlds are unloaded, but I'm too tired to go digging around for that thread again.)
So then I further tested without CBE-wirelessredstone and found that if I deleted a world (W01) that had just been created then created a new world (W02) with a new name then Thaumcraft reported errors of not finding aurra node data in the world (W01) that was just deleted. Obviously the files no longer existed, but why was Thaumcraft trying to access them in the first place? I created a new world, why would Thaumcraft need to look to the old one for aura nodes?
I then disabled Thaumcraft. Still... leaking consecutive worlds but at least nothing was reported actively trying to access them. Finally I added ChickenChunks to my disable list. Now I have disabled ChickenChunks, mystcraft, PortalGun, Thaumcraft, ThaumicBees, TwilightForest, and all three CBE-wirelessredstone. I have now made 4 consecutive worlds with no leak reports.
-- End history --
I would like to know if you finished thinking about the problem you mentioned =) If so, would you please let me know what you discovered?
I have not tried your second fix. I will, eventually; I love all of these mods and intend to use them on my server (memory leak in consecutive worlds should not be a problem). I will, however, investigate an alternative to CBE-Wirelessredstone. The original wirelessredstone mod has a version available for 1.4.7 (which is the Minecraft version we are all using on FTB at the moment).
Thank you
(P.S. No logs are posted because I am not trying to have something debugged... yet. Just requesting follow-up info for something BTG posted.)
