-
Notifications
You must be signed in to change notification settings - Fork 9
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
[1.18.2][BUG] Memory Issues #41
Comments
Closing as it might have been a red-herring. Will re-open if need be. |
Preface: Data: Only Immersive Engineering installed, the heap space is around 395 mbs In all these tests it had around a 216mb garbage per minute gain https://i.imgur.com/dDDwaf4.png https://i.imgur.com/UtqFp9g.png https://i.imgur.com/IVRNbmd.png https://i.imgur.com/kAUSz6w.png Adding just Immersive Posts, the heap jumps to around 1.05 gbs. In all of these tests it had around a 218mb garbage per minute gain. https://i.imgur.com/vR6Tn5g.png, https://i.imgur.com/qL1Itiw.png, https://i.imgur.com/hv1vJqQ.png, https://i.imgur.com/4IgYtbs.png, https://i.imgur.com/fCzors0.png Heap Dump for Immersive Enginneering: https://i.imgur.com/CHPyUlm.png Heap Dump for Immersive Engineering + Posts: https://i.imgur.com/50zXkwk.png Conclusion Aside |
I'm also experiencing memory issues with this installed. It's causing a lot of lag on the client due from the GC |
Is there an existing issue for this?
Are you using the most recent version of X?
Minecraft Version
1.18.2
Forge Version
40.1.48
Immersive Engineering Version
1.18.2-8.0.1-147
Related Mods and their Versions
Nothing specific, though the more blockstates there are the worse it gets
Current Behaviour
Memory leak related to blockstates
Expected Behaviour
No memory leak?
Reproduction Steps
Have mod installed
leak Memory
Logs
https://mclo.gs/FOzx4HD
Additional Informations
With mod at main menu: https://i.imgur.com/6SBVjmA.png
Without mod at main menu: https://i.imgur.com/Q0JS0kq.png
If you've never seen VisualVM before the dips are GC.
I can provide a heapdump, but given the nature of heap dumps it would be quite large and finding a place to upload would not be easy.
The text was updated successfully, but these errors were encountered: