-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: ClaimHandler.read can cause a watchdog timeout #16
Comments
The method that its timing out on is literally a vanilla call |
OK, well that doesn't rule out Cadmus from being at fault in particular. Is there a chance that the NBT it's trying to save is huge/wrong in some other way? |
the nbt for cadmus is very small like extremely small, its 8 bytes per chunk and then 38 bytes for the key so if you had 100k chunks thats less than an mb |
This is odd then. I've done a mixin export and |
Have you ran into this any more times since the initial report? I've been unable to reproduce it, and as gravy said, it's watchdoging on a vanilla call. Perhaps one of the other mods you have installed is messing with nbt reading? |
It still occurs every time the reproduction step happens, but I haven't updated the pack in a while so it might have been fixed. The mixin export didn't show anything immediately suspicious but I didn't look too deep into it |
Bug Description
The methods
earth.terrarium.cadmus.common.claims.ClaimHandler.read
andcom.teamresourceful.resourcefullib.common.utils.SaveHandler.read
can timeout the server and cause it to be killed by the watchdog.I have specifically ran into this twice through the
earth.terrarium.cadmus.common.claims.ClaimApiImpl.canDamageEntity
method.How to Reproduce?
This is how we've caused it, twice:
Expected Behavior
The method should not trigger the watchdog 😆
Version
1.0.0
Mod Loader Version
1.20.1 0.19.2
Mod Loader
Quilt
Logs or additional context
https://mclo.gs/luPwtPQ
Code of Conduct
The text was updated successfully, but these errors were encountered: