Bug: Event Hook causing low TPS on Multiplayer Server MC 1.19.2
xkobalx opened this issue ยท 8 comments
What Type of Bug Is This?
Performance
Forge Version
43.2.21
The Aether Version
1.19.2-1.0.0-beta.1.2-forge
Steps to Reproduce
Only effecting some players.
On player log in.
This event appears on the profiler and there are constant tps issues.
This event is triggering no matter what dimension the player is in or where they are in those dimensions.
The issue will sometimes disappear for a minute or two before resuming.
The image shows 10% but it has gone as high as 25%.
Effected players log out.
The issue stops immediately.
What You Expect To Happen
The event should not be constant and should not be using so much of the servers resources.
What Actually Happened
Event triggering when certain players log in causing TPS issues.
Additional Details
Issue persists on the effected players between reboots and logins.
Other players have been to the Aether, to the same areas and have completed the same content but are not effected.
Dedicated Server
Server is running Java 17.0.8.1
AMD Ryzen 9 5950x
16GB of 64GB RAM allocated to MC
Running on NVME RAID.
Please Read and Confirm The Following
- I have confirmed this bug can be replicated without the use of Optifine.
- I have confirmed this bug is on the most recently supported version of Minecraft.
- I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
- I have confirmed this issue is unique and has not been reported already.
- If playing on a modpack, I have reported this issue to their issue tracker already.
Can additionally confirm this, with Forge 43.3.0 and the same Aether version/ no optifine/custom modpack. This issue appears with the config option "Disables falling into the Overworld" set to TRUE and before any player on the server has even entered the aether.
See(as one example); https://spark.lucko.me/IJLpxSULDc
EDIT: notably, seems to happen to a player that has placed the portal and then not gone in. will update if that fixes the issue.
I need to rearrange the checks starting here:
A commit has been pushed that may fix this issue, it will need testing: https://output.circle-artifacts.com/output/job/0dcf30b1-84de-47b2-b572-fc07fc27bbe2/artifacts/0/~/project/build/libs/aether-1.20.1-1.0.0-beta.1.4-neoforge.jar
Could we get the beta jar with the fix for 1.19.2 as well, or would the fix be the same if I backported the relevant commit and built it myself?