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.19: Accessing LegacyRandomSource from multiple threads #307

Closed
McNasties opened this issue Nov 21, 2022 · 8 comments
Closed

1.19: Accessing LegacyRandomSource from multiple threads #307

McNasties opened this issue Nov 21, 2022 · 8 comments
Labels
Mod issue Caused by a bug in the mod, not the pack

Comments

@McNasties
Copy link

IllegalStateException randomly. Freezes, saves game, and closes.
crash-2022-11-21_10.11.44-client.txt

@roguethedev
Copy link

Hello I'm having similar error. This error occurs just randomly, sometimes take hours or maybe minutes.

I'm playing Singleplayer at Mac M1 Pro 16gb using Curse Forge app to launch, I didnt change nothing at the modpack files

Description: Accessing LegacyRandomSource from multiple threads

crash-2022-11-29_13.52.50-client.txt

crash-2022-11-29_13.39.18-server.txt

I don't know if is the map corrupt, or if the Mac its not recomend to play ATM, any help will be welcome.

@NoMoreStars
Copy link

Just got a similar crash as well

@Ninjawolf0007
Copy link

I thought this was related to an EvilCraft issue, but after the update to version 1.0.7 of ATM8, I'm also seeing this crash seemingly unrelated to a specific mod from what I can gather.
crash-2022-12-24_14.58.42-client.txt

@ghost
Copy link

ghost commented Dec 27, 2022

I believe this is caused by Supplementaries which in this commit here
common/src/main/java/net/mehvahdjukaar/supplementaries/common/block/blocks/PedestalBlock.java:152
introduces a piece of code that apparently is thread unsafe and can cause crashes like this

This change is included in ATM 8 1.0.7

Edit: level.random seems to be used several places in the Supplementaries update

@TelepathicGrunt
Copy link

TelepathicGrunt commented Dec 29, 2022

@alekthefirst No, the block's use method is ran only on server thread where it is safe to use level.random. The issue is someone is using the level's random on an off thread instead of server thread. Common places people accidentally misuse the wrong random is during worldgen or within entity constructors/finalizeSpawn mehods which also runs on off thread during worldgen. Nothing in that Supplementaries commit stands out.

@TelepathicGrunt
Copy link

TelepathicGrunt commented Dec 29, 2022

EvilCraft did make a change in dev to fix the randomsource crash as they seemed to have narrowed down themselves as a potential cause of it: CyclopsMC/EvilCraft@b03ed5e

Or at least shield themselves so they can't be blamed for someone else's misuse of the random sources (If EvilCraft was actually a victim)

@Mitchell5200 Mitchell5200 added the Mod issue Caused by a bug in the mod, not the pack label Jan 18, 2023
@Mitchell5200
Copy link
Contributor

Mod at fault identified, and mod dev contacted,
Duplicate of #307, #447, #553, #580, #649

@Mitchell5200
Copy link
Contributor

Fixed in 1.0.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mod issue Caused by a bug in the mod, not the pack
Projects
None yet
Development

No branches or pull requests

6 participants