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

[1.18.2] Crash on world load - kotlin.UninitializedPropertyAccessException #12

Closed
erunseelie opened this issue Jul 15, 2022 · 4 comments · Fixed by #28
Closed

[1.18.2] Crash on world load - kotlin.UninitializedPropertyAccessException #12

erunseelie opened this issue Jul 15, 2022 · 4 comments · Fixed by #28
Labels
bug Something isn't working

Comments

@erunseelie
Copy link

Hi, I got this crash report on loading into a world I had recently started:
https://bytebin.lucko.me/iKku4MUszR

kotlin.UninitializedPropertyAccessException: lateinit property GATE_PLACEMENT has not been initialized

I hadn't placed any WR items yet, so I'm not immediately sure what could have led to this.

@Kneelawk
Copy link
Owner

It looks like this error was encountered as NotEnoughCrashes was already generating a crash report for something else.

If you can give me any steps to reproduce, that would be much appreciated :)

@Kneelawk
Copy link
Owner

Kneelawk commented Jul 17, 2022

From what I can tell, this error was caused by NotEnoughCrashes attempting to generate a crash-report that involved rendering the world for some reason. However it attempted to render a world before having fully loaded all client-side assets, meaning that the shader had not been initialized yet.

The core-shader-based system I'm using for fancy gate placement ghosts is deprecated and I'm planning to replace it with a system that's more Iris/Canvas shader-friendly that hopefully shouldn't be as vulnerable to this problem. I'll close this when that system is implemented. It shouldn't be too hard to back-port that system to the 0.3.x-1.18.2 branch either.

@erunseelie
Copy link
Author

Got it, sure. Sorry for no initial response, I was trying to see if it would happen again, as there weren't any real steps leading to the initial crash. If it reoccurs, I'll see if it happens without NotEnoughCrashes and follow up.

@Kneelawk Kneelawk added the bug Something isn't working label Dec 17, 2022
@Kneelawk
Copy link
Owner

Kneelawk commented Jan 2, 2023

Ok, the fix for this should be out in v0.3.10+1.18.2 and v0.4.13+1.19.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants