Skip to content
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

Memory leak and world lag #70

Open
Pootleris opened this issue Mar 1, 2024 · 1 comment
Open

Memory leak and world lag #70

Pootleris opened this issue Mar 1, 2024 · 1 comment
Labels
bug A problem with the mod

Comments

@Pootleris
Copy link

Pootleris commented Mar 1, 2024

I'm on Forge 1.20.1 latest mod version (1.0.2-beta)

when i place even a simple contraption like a gantry carriage my log console gets spammed with
'[Server thread/WARN] [or.va.co.im.sh.Ak/]: Received physics frame update for ship with ShipId: 118, but a ship with this ShipId does not exist!'

i eventually have to quit or stop the contraption.

modList.txt

@blockninja124
Copy link
Contributor

blockninja124 commented Dec 8, 2024

Not sure what OP did to cause this with any contraptions, but I was able to re-create this with a constantly disassembling gantry. Problem is, each time it disassembles it deletes its ship. Then for a few frames VS is confused, receiving updates for a non-existent ship. This is... technically intended behaviour. However on a larger scale this could cause sever lag quite quickly (I already managed to get VS to think it was running behind once already). As for how we could fix this, perhaps we could change gantries to have a 'only disassemble when anchor destroyed' mode?

My setup:
image

My logs after a few minutes:
(starting from when I turned it on)
log.txt

@blockninja124 blockninja124 added the bug A problem with the mod label Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A problem with the mod
Projects
None yet
Development

No branches or pull requests

2 participants