Applied Energistics 2

Applied Energistics 2

156M Downloads

Tick taking exceedingly long causing server crash

mcer1 opened this issue ยท 7 comments

commented

Describe the bug

As soon as I try to load the chunks where my base is the server immediately stops responding. I suspect this is due to AE as when I use Amulet to delete the chunk with my ME Disk the server loads the chunk fine. Is there any way I can recover my items from the system?

How to reproduce the bug

I'm not entirely sure how to reproduce this issue as it occurred randomly at a point. I always gracefully shut off the server so it wasn't something I expected.

Expected behavior

The chunk should load fine

Additional details

I did try to remove the modernfix mod as the error log suggested but it did not fix the issue.

Which minecraft version are you using?

1.21

On which mod loaders does it happen?

Forge

Crash log

https://pastebin.com/s36dcBh4

commented

And what would make you think that there is a strong indication that AE2 is involved here? Without more information this is pure speculation in my eyes.

Seeing that this is a quite large modpack (which one btw?): Have you tried the appropriate support channels for that modpack before coming here?

commented

@mcer1 Please install https://www.curseforge.com/minecraft/mc-mods/fullstack-watchdog and see if you can get another watchdog crash-report.

commented

Hello, Yeah I can see that there isn't a direct mention of AE2. However, as I mentioned in the post, there does seem to be a strong indication that it is AE2. Would it be a reasonable task to modify the nbt data (possibly by simply removing all applied energetics related settings) and seeing if it starts to work? If this is something that is possible it would help ascertain whether or not AE2 is the culprit. I'm not very experienced with this so I'm just wondering how hard it would be to test whether it is AE2 that is causing it. Alternative I was thinking about removing AE2 entirely (difficult because other mods rely on it) or trying to copy the data to a server instance with only AE2 and seeing if it hangs.

You can do that, yes, The bigger issue here is that you don't actually see the full stack trace for the Server thread in your crash report, and I really don't know why that is. I hope that is not some mod abbreviating the crash report.

What I mean is that the key information is actually hidden by the ... in this crash report section:



"Server thread" prio=8 Id=127 TIMED_WAITING on java.lang.String@77ddeb98
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	-  waiting on java.lang.String@77ddeb98
	at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
	at TRANSFORMER/[email protected]/net.minecraft.util.thread.BlockableEventLoop.m_5667_(BlockableEventLoop.java:521)
	at TRANSFORMER/[email protected]/net.minecraft.util.thread.BlockableEventLoop.m_18701_(BlockableEventLoop.java:141)
	at TRANSFORMER/[email protected]/net.minecraft.server.level.ServerChunkCache.m_7587_(ServerChunkCache.java:131)
	at TRANSFORMER/[email protected]/net.minecraft.server.level.ServerChunkCache.m_8475_(ServerChunkCache.java:113)
	at TRANSFORMER/[email protected]/net.minecraft.server.level.ServerChunkCache$$Lambda$52228/0x0000000806200000.get(Unknown Source)
	at [email protected]/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	...

p.s.: It'a also possible a world generation thread has crashed. Check your log file for errors before this watchdog triggers.

commented

@TelepathicGrunt Your mod had another happy customer :-D

commented

Seeing that this is a quite large modpack (which one btw?)

The modpack is All the Mods 9 - No Frills

Without more information this is pure speculation in my eyes.

You ended up being right about that. After using the fullstack-watcdog mod shartte told me to add I could see that starlight was causing the crash. Removing it fixed the issue.

Thank you shartte and Mithi. I apologize for bringing up the issue to you guys first

commented

Hi, your report contains no mention of AE2 in any of the running code, although the sections per thread seem to be abbreviated so much they're kinda useless.

Without any lead as to why AE2 is supposed to be the culprit here, I don't know how to help you here.

p.s.: You selected 1.21, but the crashlog is for 1.20.1

commented