This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
njdart's profile picture

[1.57/1.58][SSP] Something blocking main thread in the Direwolf20 pack

Started by njdart, 22 March 2014 - 11:38 PM
njdart #1
Posted 23 March 2014 - 12:38 AM
Using the Direwolf20 pack (V1.0.18, MC1.6.4), something is blocking the main thread.
Tried using the supplied and latest versions of CC and all the Open mods. no luck

Happens on chunk load, fine otherwise. we're using lots (50+) of network cables and wired modems.

Removed all the Open mods, problem persists, removed CC as well, problem "resolved". although not desirable fix.

Map Download: http://42nd.org/njda...2-45-24).tar.gz

problem is in "nexus red", go to the ugly cobble stone building near spawn, through the mystcraft portal. (Dimension 6)

the only "useful" information we've managed to get is as follows:
Bomb Bloke #2
Posted 23 March 2014 - 02:04 AM
This sounds very familiar. Just to be clear, you're saying that the server thread is locking up completely? Does it do this as soon as the chunk loads, or…?
njdart #3
Posted 23 March 2014 - 02:24 PM
As soon as the chunk loads, we can't even log in, it deadlocks right away
Bomb Bloke #4
Posted 24 March 2014 - 12:24 AM
Ouch. Usually ComputerCraft has the courtesy to give you at least a few minutes of run time before stalling servers. I gave it a try, and indeed the server locked immediately after entering the specified dimension.

I pulled out all the Open mods, updated ComputerCraft to the 1.6pre7 release, and it worked. So that at least looks promising… Note, though, that the Open mods likely won't see a compatibility update for 1.6 until it sees a proper "stable" release, and there's still some (other) major bugs to be squashed before that happens.

To be sure, I then reverted back to CC1.57 and tested again - sure enough, instant lock-up. I notice that you've already pulled out the disk files for all the computers and turtles, so that points the finger squarely at block placement… Switching between the pre-release and an old "stable" build, it should be possible to pin-point the exact "peripheral" at fault, remove it, and get on with playing.