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
Crash reported by maccollo #872
Comments
INFO file for a second crash: https://gist.github.com/eggrobin/aa32c5a4897073ad62c8, stack trace:
|
From the journal and info log provided by maccollo: The call being executed is:
In The three segments look like:
The alert reader will notice that 3722304989 = 0xDDDDDDDD. In other words, we stomped on memory. |
Another instance of this reported by Flord, resulting in
The stack trace is
Decoded stack trace: |
And idem, ibidem,
Stack:
Decodes identically to the above. |
@tuffzinator reports a crash that's probably another instance of this, https://gist.github.com/tuffzinator/3d4ddf6a5c9cf7cd9722. |
…est#872 (mockingbirdnest#908 could be an instance of this).
FATAL:
The text was updated successfully, but these errors were encountered: