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.

Sign up for GitHub

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

Jump to bottom

Sodium crashes when sodium-options.json is corrupt. #219

Closed
LucilleTea opened this issue Jul 31, 2020 · 5 comments
Closed

Sodium crashes when sodium-options.json is corrupt. #219

LucilleTea opened this issue Jul 31, 2020 · 5 comments
Labels
S-fixed Status: Fixed T-crash Type: Crash or hang

Comments

@LucilleTea
Copy link
Member

Reproduction Steps

  1. Have a corrupt sodium-options.json in the config folder.
  2. View sodium's settings or open a world.

Crash Report File

https://pastebin.com/61ESLENC
https://cdn.discordapp.com/attachments/602805020861267968/737681352349974668/latest.log

Additional Information

A sample corrupt file:
https://cdn.discordapp.com/attachments/602805020861267968/737956575867699275/sodium-options.json
@LucilleTea LucilleTea added the T-crash Type: Crash or hang label Jul 31, 2020
@jellysquid3 jellysquid3 added this to the Release 0.2 milestone Aug 2, 2020
This was referenced Aug 3, 2020
Closed
Closed
@deeprobin deeprobin mentioned this issue Aug 22, 2020
Closed
@amnotbananaama amnotbananaama added the S-confirmed Status: Confirmed label Aug 25, 2020
@jellysquid3 jellysquid3 mentioned this issue Aug 25, 2020
Closed
@LucilleTea LucilleTea mentioned this issue Aug 27, 2020
Closed
@amnotbananaama amnotbananaama mentioned this issue Sep 10, 2020
Closed
@amnotbananaama amnotbananaama added the R-pending-merge Resolution: Pending merge label Sep 27, 2020
@LucilleTea LucilleTea mentioned this issue Sep 30, 2020
Closed
@amnotbananaama amnotbananaama mentioned this issue Jan 26, 2021
Closed
@amnotbananaama amnotbananaama mentioned this issue Feb 4, 2021
Closed
@silversquirl silversquirl mentioned this issue Feb 20, 2021
Closed
@amnotbananaama amnotbananaama mentioned this issue Feb 22, 2021
Closed
@jellysquid3
Copy link
Member

Commit 6f1762f might resolve this.

@jellysquid3
Copy link
Member

Looks to be fixed in 1.16.x/next.

@amnotbananaama amnotbananaama added R-pending-release Resolution: Pending release and removed R-pending-merge Resolution: Pending merge labels Jun 5, 2021
@LucilleTea LucilleTea mentioned this issue Jun 10, 2021
Closed
@silversquirl silversquirl mentioned this issue Aug 28, 2021
Closed
@silversquirl
Copy link
Member

This is apparently happening again in 0.3.0, see #862

@silversquirl silversquirl reopened this Aug 28, 2021
@amnotbananaama amnotbananaama mentioned this issue Sep 6, 2021
Closed
@jellysquid3 jellysquid3 removed this from the Release 0.2 milestone Sep 22, 2021
@jellysquid3 jellysquid3 added this to the Sodium 0.3.3 milestone Oct 29, 2021
@amnotbananaama amnotbananaama mentioned this issue Nov 18, 2021
Closed
@MeeniMc
Copy link
Contributor

MeeniMc commented May 11, 2023

As of 0.4.11 (presumably earlier) a correct error screen is shown and proposes to reset the problematic option files. Issue is resolved.

@pajicadvance pajicadvance removed the S-confirmed Status: Confirmed label May 11, 2023
@pajicadvance pajicadvance added S-fixed Status: Fixed and removed R-pending-release Resolution: Pending release labels May 11, 2023
@pajicadvance
Copy link
Member

Not sure when exactly this was fixed either, but Sodium 0.4.10 now shows this screen and the game can proceed to run normally. Thanks for the bump.

Screenshot_4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S-fixed Status: Fixed T-crash Type: Crash or hang
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jellysquid3 @amnotbananaama @silversquirl @pajicadvance @LucilleTea @MeeniMc