-
Notifications
You must be signed in to change notification settings - Fork 31
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
[SOLVED, 1.0.10+] Accessing LegacyRandomSource from multiple threads #649
Comments
I have been crashing a lot lately as well (I think it's been worse after the last update?). I've gotten 3 CTD's just this evening. The last one had this error message too. I'll leave my crash report here in case it helps (my other 2 CTD's were "Ticking Entity"). *Edit, January 15: I've had a stable game for a few days, but today I got this same error again. I'm adding a second error report, I hope this helps somehow. :) crash-2023-01-12_21.58.20-client.txt |
... and another one. Please let me know if you need any more info or if anyone know how to potentially fix this. The crash log is attached. |
Yup, it seems as if something is causing problems, I just had another CTD with this error code. Unfortunately, I don't understand the crashlog but I hope it can be of use. :( |
Awesome, thanks a lot! |
Yes thank you! I haven't been able to play because of the crashing. It really is random, could take a couple of hours or just a few mins and I crash again. I had no issues until I got further and further into the mod pack. I do have the Ars mage light around my base, first time I really have dove into Ars. I saw the comments about Ars mage lights, so figured I would mention it. I have not touch Evil Craft at all, I usually don't. The crash usually happens when I am in a loaded chunk. I do have a handful of compact machines that are loaded. |
Fixed in 1.0.9 |
Nope. Issue still present in 1.0.9. No crash log is generated |
yes, sorry, we falsely believed it was fixed, further investigation has pointed at evilcraft again, and another modder found it to be the true cause for 90% of the issues, the information has been passed on and hopefully it will be fixed soon I'm also going to Pin this issue as it's clearly still active despite our previous information |
No problem. It did generate a crash log btw I was just blind. |
This seems to be fixed as of the last patch. Haven't had any issues since |
Solved post 1.0.10, closing |
crash-2023-01-11_19.31.36-client.txt
Can anyone help me figure out why I keep crashing? It has been the same error for 2 weeks now. I can't even play and it is very frustrating. Would love some more direction as to why I keep crashing. I have tried to read over the crash report to see if anything stands out but reading these things can get a bit confusing. When I have Googled this type of crash, all I have come up with is resource packs or shaders. Not sure how accurate that is.
The text was updated successfully, but these errors were encountered: