-
-
Notifications
You must be signed in to change notification settings - Fork 946
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
Crashlog truncated with many news messages #7255
Comments
Possible Fix: Depending on the amount of memory left for OpenTTD to allocate and the number of news messages, dynamically calculate and allocate the buffer to writing the OpenTTD crash report, instead of just assuming you will have no more than some number of recent news messages at the time of the crash and allocating a fixed buffer length for the crash report. |
This issue has been automatically marked as stale because it has not had any activity in the last two months. |
… most recent news messages
… most recent news messages
… most recent news messages. (OpenTTD#7542)
… most recent news messages
Version of OpenTTD
After merge of #6709
Expected result
Crashlog written in full including the footer
*** End of OpenTTD Crash Report ***
.Actual result
File is truncated after a fixed buffer length is exhausted.
Steps to reproduce
Load a savegame which produces a large number of news messages, for example gr0_50k_stations63 used for testing #7235. This game will produce a very large number of station acceptance news messages on the first day of loading. If a crash occurs before these news messages expire from "recent", the crash log is truncated.
The text was updated successfully, but these errors were encountered: