First of all: this mod has always been on my top 10 list from day one. Needs to be said.
Yet I am having some troubles with it lately. These issues started to my recollection with MC 1.6.2 and I am still having it with 1.6.4.
My current environment is MC 1.6.4, Forge 9.11.1.916, Inventroy Tweaks 1.56-b77 and over 70 mods - amongst others Forestry, Ironchests 2, Backpacks (both Brad16840 and Eydamos) (all the latest 1.6.4 compatible versions).
Now the problem I am having is that the client is rather often crashing while sorting inventories due to what seems to be a memory leak.
Whenever that happens I see that the javaw process itself starts eating up all memory until it inevitably dies. Unfortunately after that there will be neither a crash report nor any entries in the Forge log indicating a problem.
I already tried to figure out how to reproduce this behaviour and it seems to me that it has something to do with the amount of consumed inventory space and the variety of items involved.
So at the moment I would say that if I'll take an inventory with at least 54 slots, above 75% full and at least 20 different items the anomality happens
very unlikely with vanilla chests
rarely with Ironchests unless I stuff a lot of different Forestry bees in there
quite likely with Eydamos' backpacks
at a 75% chance with Brad16840s backpacks
I am aware that this is not much information I could provide - of course I don't even know if these issues are at all induced by InventoryTweaks.
Anyway ...at the moment I circumvent the problem by not sorting non-vanilla chests.
1
Yet I am having some troubles with it lately. These issues started to my recollection with MC 1.6.2 and I am still having it with 1.6.4.
My current environment is MC 1.6.4, Forge 9.11.1.916, Inventroy Tweaks 1.56-b77 and over 70 mods - amongst others Forestry, Ironchests 2, Backpacks (both Brad16840 and Eydamos) (all the latest 1.6.4 compatible versions).
Now the problem I am having is that the client is rather often crashing while sorting inventories due to what seems to be a memory leak.
Whenever that happens I see that the javaw process itself starts eating up all memory until it inevitably dies. Unfortunately after that there will be neither a crash report nor any entries in the Forge log indicating a problem.
I already tried to figure out how to reproduce this behaviour and it seems to me that it has something to do with the amount of consumed inventory space and the variety of items involved.
So at the moment I would say that if I'll take an inventory with at least 54 slots, above 75% full and at least 20 different items the anomality happens
I am aware that this is not much information I could provide - of course I don't even know if these issues are at all induced by InventoryTweaks.
Anyway ...at the moment I circumvent the problem by not sorting non-vanilla chests.