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

Opening ongoing crafting screen causes CTD #5132

Closed
CloWnicide opened this issue Apr 9, 2021 · 4 comments · Fixed by #5142
Closed

Opening ongoing crafting screen causes CTD #5132

CloWnicide opened this issue Apr 9, 2021 · 4 comments · Fixed by #5142

Comments

@CloWnicide
Copy link

Describe the bug
Opening crafting screen causes CTD

To Reproduce
Begin auto-crafting of item, open crafting screen, CTD

Expected behavior
No CTD when looking at ongoing auto-crafting

Additional context
https://gist.github.com/CloWnicide/d6b2256fe305cc531775d3c3adfffe64

Environment
Java: 11.0.1.0.0, Forge: 36.1.2, AE2 Version: 8.3.0-alpha.2
Force Crash Log: https://gist.github.com/CloWnicide/c2e8ba13a522e8b62feaba3c509aaec1

@Technici4n
Copy link
Member

We don't support optifine, please try again without it.

@SAGESSE-CN
Copy link

i had the same issue not long ago, but it not a ae issue, you can't any support in here.

optfine and forge has some compatibility problems, someone use optfore mod to fix it.

good lucky.

@shartte
Copy link
Member

shartte commented Apr 11, 2021

I can in theory see how this happens. Do you by chance have a slow network connection?

@shartte shartte reopened this Apr 11, 2021
@shartte
Copy link
Member

shartte commented Apr 11, 2021

Reproduced by forcefully slowing down GUI syncs between server->client.

This is a race-condition and should happen rarely. Will look into fixing this.

shartte added a commit that referenced this issue Apr 11, 2021
…d have a null CPU name even though the noCPU flag was false.
yueh pushed a commit that referenced this issue Apr 11, 2021
…d have a null CPU name even though the noCPU flag was false. (#5142)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants