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

Obscure startup crash involving OpenSecurity #15421

Closed
2 of 3 tasks
divine-ray opened this issue Jan 26, 2024 · 6 comments
Closed
2 of 3 tasks

Obscure startup crash involving OpenSecurity #15421

divine-ray opened this issue Jan 26, 2024 · 6 comments
Labels
Crash Status: Stale Automatically close this issue in 2 weeks if there are no new responses Status: Triage Issue awaiting triage. Remove once this issue is processed

Comments

@divine-ray
Copy link

Your GTNH Discord Username

divine_ray

Your Pack Version

2.5.1

Your Server

Private Server

Java Version

Java 8

Type of Server

Vanilla Forge

Your Actions

The game enters a state of suspense/not responding, whilst producing a crash, after the loading bar hits 33% (Hunger Overhaul). Scrolling up the log output shows that all OpenComputers addons failed to initialise due to a error in OpenComputers.
So far the only fix i found to this was to delete the config of OC and to try again, which typically works.
Note that this issue only occurs after closing down prism completely or changing mods.

(I haven't tried if this issue exists with nightly builds of OC due to not wanting to update the server for me and clients)

Crash Report

https://mclo.gs/OXWGNFp

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.
@divine-ray divine-ray added Status: Triage Issue awaiting triage. Remove once this issue is processed Crash labels Jan 26, 2024
@chochem chochem changed the title Obscure startup crash involving OpenComputers Obscure startup crash involving OpenSecurity Jan 26, 2024
@chochem
Copy link
Member

chochem commented Jan 26, 2024

hmm, does this still happen with OpenSecuritiy 1.1.1-GTNH? It almost looks like someone potentially fixed this by moving recipes from preinit to init.

@chochem
Copy link
Member

chochem commented Jan 26, 2024

but yea, maybe that is just by chance and your config file is corrupted as the error suggests. Have you tried what it says?
Error parsing configuration file. To restore defaults, delete 'OpenComputers.cfg' and restart the game.

@divine-ray
Copy link
Author

I have to delete the opencomputers.cfg file every startup in which configuration or mods changed.

@bombcar
Copy link
Member

bombcar commented Jan 26, 2024

I have to delete the opencomputers.cfg file every startup in which configuration or mods changed.

I swear there is/was a bug with opencomputer configfiles that I either investigated .... or tried to fix

yeah it's GTNewHorizons/OpenComputers#114 - but that's post 2.5.1

Maybe that fix would fix your issue?

@glowredman
Copy link
Member

Did you just update or were you running 2.5.1 for a while? If you just updated, which version did you play on before? Seems to be similar to #14364. in that case, the solution would be:

  1. Go to the root directory of the modpack
  2. Open localconfig.cfg
  3. Remove the line which starts with OpenComputers.cfg/opencomputers.client/*:nanomachineHudPos=

@divine-ray
Copy link
Author

i've been running 2.5.1 since about mid december-ish, but fiddled with various extra mods (JM unlimited, worldedit, JEC, etc.) since then
image
my localconfig.cfg file; no nanomachineHudPos to be seen.

https://mclo.gs/ek2zcAa here's a crash log of such incident, in case that it is relevant

@mitchej123 mitchej123 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
@mitchej123 mitchej123 added Status: Stale Automatically close this issue in 2 weeks if there are no new responses Comment to reopen labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crash Status: Stale Automatically close this issue in 2 weeks if there are no new responses Status: Triage Issue awaiting triage. Remove once this issue is processed
Projects
None yet
Development

No branches or pull requests

5 participants