Crash reports after latest update
-
The attached crash log is due to you using the donor client with a non-donor account.
I noticed that the log is from 6 days ago, so it possibly is not the correct one. The latest.log has no errors, so it might be useful to enable the output log and send the contents of that after the crash
-
Ah sorry, didn't look at timestamp, I assumed those crashes made crashlogs but I guess they didn't as that's the most recent one I have
The donator client issue was resolved, my mistake
It seems like the copy paste function on output logs is bugged, when trying ctrl + a, ctrl + c or highlighting all and copying from right click, only ~50 lines copy. There are 550 lines in this so I can't copy it all
Just scrolling through the log, this is where I believe the crash is happening -
Also, here's the latest if it helps at all - latest.txt
Once again no crash log was made in \crash-reports
I was again able to replicate the crash fairly quickly after a handful of toggles on and off with xray
If anything else is needed let me know, thanks again -
It's due to Sodium. Uninstall it for now while we look into it.
-
-
-
-
Can you please help, not sure why it's still crashing...
-
@wankaewo said in Crash reports after latest update:
There is no crash in this file. Please send the output log contents (enabled in launcher settings) if this still occurs
|