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

Crashes after entering a specific area #16272

Closed
2 of 3 tasks
ART33 opened this issue May 14, 2024 · 4 comments
Closed
2 of 3 tasks

Crashes after entering a specific area #16272

ART33 opened this issue May 14, 2024 · 4 comments
Labels

Comments

@ART33
Copy link

ART33 commented May 14, 2024

Your GTNH Discord Username

No response

Your Pack Version

2.5.1

Your Server

SP

Java Version

Java 8

Type of Server

Single Player

Your Actions

I teleported to an area in the main world where I deployed a basic pump and a combustion Generator, and then the game crashed.
屏幕截图 2024-05-14 143800
Crash Report: https://mclo.gs/Lnmoxlo

Unable to re-enter the world:
image
Crash Report: https://mclo.gs/t9VEwgC

The crash still exists after restoring the latest backup. Unfortunately, the backups from earlier in the day seem incompleted due to the shortage of storage space and the backups from the previous day were removed permanently due to the same reason.

It seems like world corruption after searching in issues, so I also tried to replace the following files from a new-created world with the same seed, but the issue still exists:

level.dat
level.dat_mcr
level.dat_old
session.lock

I am looking for a way to solve this issue, please let me know if more information is needed. Thanks!

Crash Report

https://mclo.gs/Lnmoxlo
https://mclo.gs/t9VEwgC

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.
@ART33 ART33 added Status: Triage Issue awaiting triage. Remove once this issue is processed Crash labels May 14, 2024

This comment was marked as outdated.

@Glease Glease added Type: World Corruption i.e. nothing we can do about it beyond load a backup. and removed Status: Triage Issue awaiting triage. Remove once this issue is processed labels May 15, 2024
@Glease
Copy link
Contributor

Glease commented May 15, 2024

What's your seed then?

@Glease Glease removed the Type: World Corruption i.e. nothing we can do about it beyond load a backup. label May 15, 2024
Copy link
Contributor

Found 2 linked crash report(s)

Primitive Automated Analysis of Crash Report

https://mclo.gs/Lnmoxlo
This crash report suggests world corruption. Try restore from a backup.

Primitive Automated Analysis of Crash Report

https://mclo.gs/t9VEwgC
This crash report is near useless. Try post fml-client-latest.log instead.

@ART33
Copy link
Author

ART33 commented May 15, 2024

What's your seed then?

Thanks, the issue is solved. Removed all corrupted chunks. Closing issue.

@ART33 ART33 closed this as completed May 15, 2024
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

2 participants