"This is NOT a bug, but may mean a computer is misbehaving"

[s-sx-x]

[04Okt.2022 04:14:47.352] [ComputerCraft-Computer-Monitor-0/WARN] [computercraft/]: Terminating computer #7 due to timeout (running for 10.012230663 seconds). This is NOT a bug, but may mean a computer is misbehaving. ComputerCraft-Computer-Runner-1 is currently WAITING
  on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@78f84425
  at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
  at [email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
  at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
  at [email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
  at [email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
  at [email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
  at TRANSFORMER/[email protected]/cc.tweaked.internal.cobalt.LuaThread.run(LuaThread.java:485)
  at TRANSFORMER/[email protected]/cc.tweaked.internal.cobalt.LuaThread.run(LuaThread.java:433)
  at TRANSFORMER/[email protected]/dan200.computercraft.core.lua.CobaltLuaMachine.handleEvent(CobaltLuaMachine.java:187)
  at TRANSFORMER/[email protected]/dan200.computercraft.core.computer.ComputerExecutor.resumeMachine(ComputerExecutor.java:654)
  at TRANSFORMER/[email protected]/dan200.computercraft.core.computer.ComputerExecutor.work(ComputerExecutor.java:624)
  at TRANSFORMER/[email protected]/dan200.computercraft.core.computer.ComputerThread$TaskRunner.run(ComputerThread.java:550)
  at [email protected]/java.lang.Thread.run(Thread.java:833)
[04Okt.2022 04:14:48.272] [ComputerCraft-Computer-Runner-1/ERROR] [computercraft/]: Error running task on computer #7
java.lang.InterruptedException: null
        at java.util.concurrent.locks.ReentrantLock$Sync.lockInterruptibly(ReentrantLock.java:159) ~[?:?]
        at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:372) ~[?:?]
        at dan200.computercraft.core.computer.ComputerExecutor.shutdown(ComputerExecutor.java:469) ~[cc-tweaked-1.18.2-1.100.9.jar%2351!/:1.100.9]
        at dan200.computercraft.core.computer.ComputerExecutor.resumeMachine(ComputerExecutor.java:659) ~[cc-tweaked-1.18.2-1.100.9.jar%2351!/:1.100.9]
        at dan200.computercraft.core.computer.ComputerExecutor.work(ComputerExecutor.java:624) ~[cc-tweaked-1.18.2-1.100.9.jar%2351!/:1.100.9]
        at dan200.computercraft.core.computer.ComputerThread$TaskRunner.run(ComputerThread.java:550) [cc-tweaked-1.18.2-1.100.9.jar%2351!/:1.100.9]
        at java.lang.Thread.run(Thread.java:833) [?:?]

Every once in a while, some of my turtles get hard killed. I've made sure they're not endless-looping.
Judging from the source, this seems to be related to a fixed timeout budget, probably when my server is throttling (not sure tho, according to the logs its not behind in ticks at the time the turtles get cancelled).

Might there by something I am overlooking?
Thanks in advance.

[fatboychummy]

Computercraft only allows computers to run nonstop for 10 seconds straight, at which point this happens.

At 7 seconds, an error is generated, "Too long without yielding." At which point if the computer does not yield after 3 more seconds, it will kill the computer and say that in the log.

10 seconds is a lot of time for code though, so it's likely an issue with the code you are using. Would you be able to post it?

[s-sx-x]

They're not getting killed anymore, but after some time when I return to them, they're still restarted.

All of them are carrying a chunk loader upgrades. Any ideas?

[s-sx-x]

Are computer IDs supposed to be unique? Because on my server, they're currently are not.

[SquidDev]

All of them are carrying a chunk loader upgrades. Any ideas?

What mod are the chunk loader upgrades from? Possibly worth reporting to them.

Are computer IDs supposed to be unique? Because on my server, they're currently are not.

If you're playing survival, they definitely should be. But it won't cause problems if they're not.

[s-sx-x]

Apparently, the Advanced Peripherals world gen spawns of computers have fucked up IDs.

That might be troublesome because every computer with the same ID also shares the same user directory on the server side. So if to computers with the same ID are trying to write to a file at the same time, best case would be one overwriting the other (which would already be kinda unfortunate); worst case who knows whats gonna happen :D

[SquidDev]

I've made a change which should make the logging a little more verbose. Would you be able to grab the artefact from here and run it, then report back with the logs next time you see an issue?