Posted 23 April 2013 - 12:47 PM
I seem to get a deadlock between 2 threads, causing a freeze of the internal server (SMP). Seems to be triggered by high wireless rednet traffic.
Nothing interesting in the forge log or stderr
Not sure how much of use would be showing my code, there are lots of it and it's a total mess, but if there's interest i'll upload it somewhere :P/>
From VisualVM: (full dump is attached)
Interesting that it seems to reference a turtle, as i only have one of them and it's not part of much rednet communication.
Looks similar to what was reported (and supposedly fixed) in http://www.computercraft.info/forums2/index.php?/topic/7987-146cc-1481smp-server-freeze-during-turtle-program/
Nothing interesting in the forge log or stderr
Not sure how much of use would be showing my code, there are lots of it and it's a total mess, but if there's interest i'll upload it somewhere :P/>
From VisualVM: (full dump is attached)
Found one Java-level deadlock:
=============================
"Coroutine-2":
waiting to lock monitor 0x00000000156dba88 (object 0x0000000785cd0de0, a dan200.computer.core.Computer),
which is held by "Server thread"
"Server thread":
waiting to lock monitor 0x000000001d3a1798 (object 0x0000000785cd0b68, a dan200.turtle.shared.TurtleModem$Peripheral),
which is held by "Coroutine-2
Interesting that it seems to reference a turtle, as i only have one of them and it's not part of much rednet communication.
Looks similar to what was reported (and supposedly fixed) in http://www.computercraft.info/forums2/index.php?/topic/7987-146cc-1481smp-server-freeze-during-turtle-program/