Java Version: Java Version 1.7.0_05 from Oracle Corporation
Antivirus Program: When running Tekkit with a 64 or 128-pixel resolution texture pack, I attempt to set Minecraft to use 1536MB memory. Resource usage monitor declares that minecraft has eaten a gigabyte of memory - however, when I enter a world, it soft-crashes the first time, and works the second time (but declares that only 247MB is allocated, and that that's the most that can be allocated). Tekkit quickly goes out of memory and crashes from then.
Strange thing is that this issue does not occur with vanilla MC with 128x - it allocates 1gb straight-up, uses allocates half that and uses half again. With a custom pack that uses IC2, RP and BC2, It allocates the full 1GB, uses about a quarter of that, and shoots up when I intentionally hard-load circuitry and computercraft scripts.
Description of Problem:
When running Tekkit with a 64 or 128-pixel resolution texture pack, I attempt to set Minecraft to use 1536MB memory. Resource usage monitor declares that minecraft has eaten a gigabyte of memory - however, when I enter a world, it soft-crashes the first time, and works the second time (but declares that only 247MB is allocated, and that that's the most that can be allocated). Tekkit quickly goes out of memory and crashes from then.
Strange thing is that this issue does not occur with vanilla MC with 128x - it allocates 1gb straight-up, uses allocates half that and uses half again. With a custom pack that uses IC2, RP and BC2, It allocates the full 1GB, uses about a quarter of that, and shoots up when I intentionally hard-load circuitry and computercraft scripts.
As an additional aside, the initial memory allocation takes upwards of 30 seconds, when it takes less than 3 for vanilla and custom-pack.
Error Messages:
Standard "Out of Memory" error, allowing a return to the main menu, otherwise OoM exception and CTD.
Question
Kwahn
Launcher Version: 1.0.1.3
Operating System: Windows XP 32 bit
Java Version: Java Version 1.7.0_05 from Oracle Corporation
Antivirus Program: When running Tekkit with a 64 or 128-pixel resolution texture pack, I attempt to set Minecraft to use 1536MB memory. Resource usage monitor declares that minecraft has eaten a gigabyte of memory - however, when I enter a world, it soft-crashes the first time, and works the second time (but declares that only 247MB is allocated, and that that's the most that can be allocated). Tekkit quickly goes out of memory and crashes from then.
Strange thing is that this issue does not occur with vanilla MC with 128x - it allocates 1gb straight-up, uses allocates half that and uses half again. With a custom pack that uses IC2, RP and BC2, It allocates the full 1GB, uses about a quarter of that, and shoots up when I intentionally hard-load circuitry and computercraft scripts.
Description of Problem:
When running Tekkit with a 64 or 128-pixel resolution texture pack, I attempt to set Minecraft to use 1536MB memory. Resource usage monitor declares that minecraft has eaten a gigabyte of memory - however, when I enter a world, it soft-crashes the first time, and works the second time (but declares that only 247MB is allocated, and that that's the most that can be allocated). Tekkit quickly goes out of memory and crashes from then.
Strange thing is that this issue does not occur with vanilla MC with 128x - it allocates 1gb straight-up, uses allocates half that and uses half again. With a custom pack that uses IC2, RP and BC2, It allocates the full 1GB, uses about a quarter of that, and shoots up when I intentionally hard-load circuitry and computercraft scripts.
As an additional aside, the initial memory allocation takes upwards of 30 seconds, when it takes less than 3 for vanilla and custom-pack.
Error Messages:
Standard "Out of Memory" error, allowing a return to the main menu, otherwise OoM exception and CTD.
Error Log:
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.