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
Random game crash #6688
Comments
bnegrut wrote:
Attachments This comment was imported from FlySpray: https://bugs.openttd.org/task/6688#comment14876 |
3298 wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6688#comment14877 |
bnegrut wrote:
Attachments
This comment was imported from FlySpray: https://bugs.openttd.org/task/6688#comment14878 |
3298 wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6688#comment14879 |
bnegrut wrote:
Attachments This comment was imported from FlySpray: https://bugs.openttd.org/task/6688#comment14882 |
Another new game. Still random crash. |
Without the dmp it will be impossible to trace the crash. |
Out of curiosity: why is the provided stack trace insufficient? |
Because, for some reasons, the provided stack trace is not decoded. and with just the addresses it's hard to know where the crash happened. |
Unfortunately, i can't upload the .dmp file. Thank you |
@glx22 yes, I saw, but you didn't answer my question. To rephrase what I meant: why can't you load the process in a debugger, attach the symbols and symbolise the trace? Or just symbolise it with stack walker, skipping the debugger? @bnegrut as long as it is smaller than 10MiB, GitHub will accept files with names ending in |
Understood. |
Thanks. ICU has known issues, and there is a project underway to replace it. We're not keeping the reports relating to it open, but they can still be found here as and when they are needed. Thanks for the report and diagnosis efforts. |
bnegrut opened the ticket and wrote:
Attachments
Reported version: 1.7.2
Operating system: Windows
This issue was imported from FlySpray: https://bugs.openttd.org/task/6688
The text was updated successfully, but these errors were encountered: