StackOverflowException in Server Tick Loop
Lemon-B-Citrom opened this issue ยท 3 comments
Modloader
Fabric
Minecraft Version
1.19.2
Modloader Version
Fabric: Loader 0.14.12 + API 0.70.0
No Chat Reports Version
1.19.2-v1.13.12
Modpack Info
No response
The latest.log File
Bug Description
Issue
I have a multiplayer world that has been ongoing for several days and it would reboot every day without issue. As of today, rebooting the server has a chance of incurring stack overflows in the server tick loop whenever the first player connects. I can not determine what causes this: sometimes the server will not crash on player connection and will function normally for a time; though it may crash later during gameplay due to a different error: https://mclo.gs/pyuAHmm. I have not performed more rigorous on mid-game crashing as it pertains to No Chat Reports.
Removing No Chat Reports seems to prevent the chance of the on-connect crash from occurring entirely, but naturally that is an unsatisfactory solution.
World Specificity
I am suspicious that the issue is world specific (creating a new world on the same server does not seem to have the same issue) https://www.mediafire.com/file/86na5kl4ekggcm7/mp2_2022-12-29_export.7z/file
Could it be related to the following log entry?
[14:55:48 WARN]: UUID of added entity already exists: class_1531['Armor Stand'/54, l='ServerLevel[mp2_2022-12-29]', x=16562064.50, y=1000.00, z=-22242911.50]
I am not sure what is spawning this armor stand, but if it somehow has the duplicate UUID of a player, could that effect No Chat Reports? Although I have seen the server crash without this message appearing.
It also, as the log indicates, may be related to advancements-- but I'm not sure how No Chat Reports would factor into that.
Steps to Reproduce
Not exactly reliably, but...
- Launch server
- Connect to server on client
- Server may shutdown with a stack overflow
Other Information
Other mods
- adorn 3.8.1+1.19.2
- amplifiednether 1.2
- architectury 6.4.62
- bclib 2.1.5
- betterdungeons 1.19.2-Fabric-3.2.1
- betterend 2.1.2
- bettermineshafts 1.19.2-Fabric-3.2.0
- betterstrongholds 1.19.2-Fabric-3.2.0
- byg 2.0.0.13
- campanion 4.1.2+fabric
- charm 4.4.4
- cloth-basic-math 0.6.1 via cloth-config
- cloth-config 8.2.88
- continents 1.1
- create 0.5.0g-796+1.19.2
- decorative_blocks 3.0.0
- fabric-api 0.70.0+1.19.2
- fabric-language-kotlin 1.8.7+kotlin.1.7.22
- fabricloader 0.14.12
- fallingtree 3.10.0
- farmersdelight 1.19.2-1.3.9
- fiber 0.23.0-2 via patchouli
- invisframes 2.2.0
- jade 8.6.3
- java 17
- jei 11.5.0.297
- lithium 0.10.4
- patchouli 1.19.2-77-FABRIC
- renameit 1.3.0+1.19
- starlight 1.1.1+fabric.ae22326
- terrablender 2.0.1.136
- terralith 2.3
- yungsapi 1.19.2-Fabric-3.8.2
- yungsextras 1.19.2-Fabric-3.1.0
I do not think the issue is on the side of No Chat Reports, especially considering the logs. Try to isolate it by removing other mods one-by-one.
I can confirm that this issue is not related to No Chat Reports as you had suspected-- the several bootups in which No Chat Report was removed and this issue did not occur were purely (un)lucky. Since then I have had the issue occur without No Chat Report, as well as not occur with No Chat Report.