Skip to content

EAI Accessing C2ME's threads leading to a crash #225

@GeorgePara61

Description

@GeorgePara61

Minecraft Version

1.20.1

Modloader

Forge

Are you using servers that accept plugins such as Bukkit or Paper?

No

Modloader Version

47.4.0

InsaneLib Version

1.21.21

EAI Version

2.7.1

Describe your issue

It appears that EAI, as the title says, accesses a thread that C2ME is using to load chunks (C2ME is a multithread chunk loading mod) causing C2ME to crash. This issue has been already reported and dismissed. I'm bringing it back, because in my understanding, EAI is at fault for trying to access a thread C2ME was loading chunks in. So maybe it could be done so that EAI can identify which threads are rendering and not access them? I have no clue, just a thought. This is the second time it happens and it is rather rare. I can set C2ME to dismiss this as a warning and not crash but after some research I understand that doing so has a small chance of leading to tick desync and corrupted states.

ThreadLocalRandom accessed from a different thread (owner: Render thread, current: Server thread)

latest.log
Wasn't able to get a debug log.

Crash Report

https://mclo.gs/qoHyBYQ

Can you reproduce with just EAI?

I have not tried

Performance Enchancers

Optifine, Other (specify under other mods)

Other mods

BadOptimizations, BetterChunkLoading, BetterFpsDist, C2ME, Connectivity, DynamicFPS, Embeddium, EntityCulling, FerriteCore, FpsReducer, ImmediatelyFast, Immersive_Optimization, ModernFix, Mobtimizations, Noisium, Oculus, Saturn, SmoothChunk, Spark, Starlight, DistantHorizons, GPUMemLeakFix.

Searched for known issues?

Checked pinned issues, Searched closed issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is neededother mod

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions