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

The game can crash with a vector-out-of-bounds exception in hashers cleanup code #685

Closed
stephengtuggy opened this issue May 17, 2022 · 7 comments · Fixed by #851
Closed
Assignees
Labels
Milestone

Comments

@stephengtuggy
Copy link
Contributor

Known Issues: The game crashed just now, after I left my ship on autopilot for about 20 minutes. It hit a vector-out-of-bounds exception on this line. Hopefully I will have this fixed within another couple of PRs or so. At least we're catching it now, rather than blithely going on into unallocated memory or something of the sort.

Originally posted by @stephengtuggy in #683 (comment)

@stephengtuggy stephengtuggy self-assigned this May 17, 2022
@stephengtuggy stephengtuggy added this to the 0.9.x milestone May 17, 2022
@LifWirser
Copy link
Contributor

20 mins on autopilot , autopilot should drop close enough to relevent nav point. Assuming you didn't crash you most likely were at "system boundery" . an overflow of somekind would be reasonable

@stephengtuggy
Copy link
Contributor Author

Perhaps I did reach the system boundary. The game still shouldn't crash. The game should almost never crash. At least not without providing some sort of "soft landing," as #681 discusses.

@BenjamenMeyer
Copy link
Member

@stephengtuggy is this still an issue? Can we defer to 0.10.x? Or do we need to close it for releasing 0.9.x?

@stephengtuggy
Copy link
Contributor Author

@BenjamenMeyer I am definitely of the opinion that this needs to be fixed before releasing 0.9.x.

@BenjamenMeyer
Copy link
Member

@BenjamenMeyer I am definitely of the opinion that this needs to be fixed before releasing 0.9.x.

Do we have a plan for fixing it?
It has been in there for several releases already; so probably not a deal breaker. Just want to make sure we have some kind of plan before we commit to delaying 0.9.0 further on account of it.

@stephengtuggy
Copy link
Contributor Author

I think I have a relatively small change that I can try. I will try to get to it tomorrow.

@stephengtuggy
Copy link
Contributor Author

I'm pretty sure that this particular source of crashes is now fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment