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

Crash in SP after MP #16553

Closed
2 of 3 tasks
barsikus007 opened this issue Jun 19, 2024 · 4 comments
Closed
2 of 3 tasks

Crash in SP after MP #16553

barsikus007 opened this issue Jun 19, 2024 · 4 comments
Labels

Comments

@barsikus007
Copy link

Your GTNH Discord Username

barsikus07

Your Pack Version

2.6.1

Your Server

SP

Java Version

Java 8

Type of Server

None

Your Actions

  1. Play on multiplayer for a while
  2. Log out and try to start singleplayer
  3. Instead of world, main menu appears
  4. Notice DimensionManager (possibly, related to galacticraft) crash in PrismLauncher logs

Crash Report

https://mclo.gs/sZc7X6L

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the crash still exists will prompt us to investigate and reopen it once we confirm your report.
  • I can reproduce this crash consistently by following the exact steps I described above.
  • I have asked other people and they confirm they also crash by following the exact steps I described above.
@barsikus007 barsikus007 added Status: Triage Issue awaiting triage. Remove once this issue is processed Crash labels Jun 19, 2024
@barsikus007
Copy link
Author

after first crash in SP, I get a less sized error log
https://mclo.gs/C9kEFch

@dimazha
Copy link

dimazha commented Jun 19, 2024

In addition:
This crash happens when a multiblock controller tries to render or something like that. If I enter in SP after MP and in there are no controllers in this world, crash doesn't happen. But as soon as I place a controller in world, I get this crash

@chochem chochem added Status: Stale Automatically close this issue in 2 weeks if there are no new responses and removed Status: Triage Issue awaiting triage. Remove once this issue is processed labels Jan 10, 2025
Copy link
Contributor

Closing this issue because it has been stale with no responses for over 7 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2025
@barsikus007
Copy link
Author

barsikus007 commented Jan 18, 2025

reopened in #18661

@github-actions github-actions bot removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants