[1.6.4][CC 1.57 & 1.58] Out of memory error [updated March 14]

The error occures with the excavate script that comes with the mod and hasn't been tested with any other mining scripts
The following version conbinations were tested:
Forge 9.10.0.845 & CC 1.58 & CC 1.57 w/ MC 1.6.4
Forge 9.11.1.916 & CC 1.57 w/ MC 1.6.4
Forge 9.11.1.953 & CC 1.57 w/ MC 1.6.4
Forge 9.11.1.965 & CC 1.57 w/ MC 1.6.4
No other mods used

Test conditions:
Fresh default world with cheats on for each combination of mods
Tested with 1 mining turtle & 1 wireless mining turtle positioned 12 blocks apart
2 double chests for unloading

The turltes were started 20 seconds apart so each was running different parts of the script with different values in memory.
With Forge 965, the turtles dug down 3 or 4 levels before stopping.
With Forger 953 they dug down 4 or 5 levels before stopping
With forge 916 and 845 they stopped after 5 or 6 levels.
Both turtles stop moving at the same time, their gui's indicate that the script is still running, but no new messages are printed on their screen
about 30 seconds later the game shutsdown with a out of memory error.

Edit:
I forgot to mention that the error also occures with a modified version of excavate from CC 1.53 that works in MC 1.5.2


Forge Log

Spoiler

2014-02-28 20:27:32 [INFO] [STDERR] Exception in thread "Thread-22" java.lang.OutOfMemoryError: unable to create new native thread
2014-02-28 20:27:32 [INFO] [STDERR]  at java.lang.Thread.start0(Native Method)
2014-02-28 20:27:32 [INFO] [STDERR]  at java.lang.Thread.start(Unknown Source)
2014-02-28 20:27:32 [INFO] [STDERR]  at dan200.computer.core.ComputerThread$1.run(ComputerThread.java:126)
2014-02-28 20:27:32 [INFO] [STDERR]  at java.lang.Thread.run(Unknown Source)
2014-02-28 20:27:32 [SEVERE] [Minecraft-Client] ########## GL ERROR ##########
2014-02-28 20:27:32 [SEVERE] [Minecraft-Client] @ Post render
2014-02-28 20:27:32 [SEVERE] [Minecraft-Client] 1285: Out of memory
…….(the GL error repeats for 23 seconds)

Client Log

Spoiler

2014-02-28 20:15:32 [CLIENT] [INFO] Reloading ResourceManager: Default
2014-02-28 20:15:35 [CLIENT] [INFO] Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:ComputerCraft Turtles, FMLFileResourcePack:ComputerCraft
2014-02-28 20:15:36 [CLIENT] [SEVERE] Using missing texture, unable to load: minecraft:textures/items/MISSING_ICON_ITEM_4259_ccprogramdisk.png
2014-02-28 20:15:36 [CLIENT] [INFO] Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge, FMLFileResourcePack:ComputerCraft Turtles, FMLFileResourcePack:ComputerCraft
2014-02-28 20:15:36 [CLIENT] [SEVERE] Using missing texture, unable to load: minecraft:textures/items/MISSING_ICON_ITEM_4259_ccprogramdisk.png
2014-02-28 20:27:32 [CLIENT] [SEVERE] ########## GL ERROR ##########
2014-02-28 20:27:32 [CLIENT] [SEVERE] @ Post render
2014-02-28 20:27:32 [CLIENT] [SEVERE] 1285: Out of memory
…. (the GL error repeats for 23 seconds)

System Specs

Spoiler

AMD FX 4100 Quad Core 3.62Ghz (graphics chipset  disabled)2GB RAMGeForce GT 420 Graphics Card w/ 1GB memoryWindows XP sp3 32bit home versionJava 1.7.0_51MC command line: -Xmx512m -XX:PermSize=256m

Edit;
After playing with this for a few moe days, It looks like CC is trying to access a recently closed thread.
Each time the turtle has locked up, has been right after a thread has been closed.

When I used 1 turtle for testing, Cc appears to use an average of 15 threads.when the game loads it's using approx. 54mb ram and 1gb of vm. This climbs at a rate of+80kb ram and +300kb vm per 2 seconds, until until it gets to approx. 524 mb and 1.1 gb when it crashes.In my latest test the error only occures when its actually mining, not when its "mining"empty air.I.E. When I crashed at level 53, i restarted it, it crashed again at level 51, then again on 49,and each crash occure shortly after a thread has been closed.for example, if the error is"[STDERR] Exception in thread "Thread-14" java.lang.OutOfMemoryError: unable to create new native thread",then it had just closed thread 14 1 or 2 seconds earlier.CC then seems to spend 30 seconds doing something (while the turtle stops moving) and after which MC crashes.Oddly enough, if you can get the turtle to respond to ctrl+t , the error won't occure

Your report doesn't mean much without having your system specs for reference, which is at least CPU, GPU, and RAM.

Sora the Hedgehog, on 07 March 2014 - 03:25 AM said:

Your report doesn't mean much without having your system specs for reference, which is at least CPU, GPU, and RAM.

You're correct about the specs, my appologies, they've been added.
You're incorrect about the lack of specs making the report less meaningfull.
Even I can see that the report indicates a memory leak in CC core, that may be infrequent in most scripts,
but is more frequent with the excavate script when used with multiple turtles.

I'm writing my own mining script and will test it with several turtle to see how frequently the error occures.