-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
TNT machines deadlock the client #36
Comments
Can you share a crash log? |
If there is no crash report, please provide the log file |
latest.log |
Huh, the logs don't seem to indicate a crash happend at all. There are a lot of warnings however, but none seem to cause any real issues. |
In this case, I'm only using Lithium, Phosphorus and Sodium. In this particular case, I ran a World Eater to replicate the crash, but it has happened before with only two TNT's. The crash happens at around 2:27. You can't see it in the recording but the common "x program doesn't respond" window triggers and Windows asks you whether to close the program or to wait. I waited for some minutes and then I closed it. During the whole process, Java consumes around 45% of the CPU. |
Have you tried without resource/datapacks? |
I tried again, without any resource/data packs loaded (only the default one), and using only Phosphorus, Lithium and Sodium. |
I replicated it again, without any resource packs in the "resource packs" folder.
Thanks for your attention! Besides this bug, your mods are amazing. |
Can you test each mod alone without the other 2 installed? This way we can find out which mod is causing it. |
I tried each mod alone for about 15 minutes, and it froze while using only Phosphor. |
I had a similar issue before with just phosphor when I was continuously generating lighting updates while a lot of lighting updates were already scheduled for that chunk. |
can confirm i also have that issue with phosphor |
i've done some testing and afaik the issue only appears in version 0.7.0 |
Reproduction Step
Crash Report File
No crash report was generated.
Additional Information
It has happened many times.
The text was updated successfully, but these errors were encountered: