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

MM-J17: NPE at End of MM game #4171

Closed
Thom293 opened this issue Feb 12, 2023 · 1 comment
Closed

MM-J17: NPE at End of MM game #4171

Thom293 opened this issue Feb 12, 2023 · 1 comment

Comments

@Thom293
Copy link
Contributor

Thom293 commented Feb 12, 2023

23:12:16,954 INFO [megamek.MegaMek] {main}
megamek.MegaMek.initializeLogging(MegaMek.java:115) - Starting MegaMek v0.49.12-SNAPSHOT
Build Date: 2023-02-12T01:37:41.488322900
Today: 2023-02-11
Origin Project: MekHQ
Java Vendor: Eclipse Adoptium
Java Version: 17.0.6
Platform: Windows 10 10.0 (amd64)
System Locale: en_US
Total memory available to MegaMek: 2 GB

As title. No obvious reason from my end.

NPE popped up like 4 times and then MM closed. I had to resolve manually with Mul.
Not sure if related, but the Ostol listed in the Salvage report was friendly. I dont think he should appear as salvage.
Screenshot 2023-02-12 005301

megamek.log
mekhq.log
autosave.sav.gz

@Windchild292
Copy link
Contributor

Windchild292 commented Feb 16, 2023

Closing as resolved, this was a MM-side break that wouldn't be recreateable without using a full suite setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants