-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Bug] Occasionally, Window Fails to Fill, Spamming Stack Trace Instead #21
Comments
I can replicate this one, it happens when a pawn is downed, there is a short delay between when they are first downed and when the word "Downed" appears on their infobox in the lower left corner, as evidenced in these two screenshots, taken moments apart: During the gap in between, if Numbers is opened, this stack trace is thrown repeatedly, regardless of columns selected, even if no columns are selected at all. |
Might be related to #17 , not sure. |
Definitely related, the above replication steps still hold, I have seen both stack traces, here is the other stack trace for reference, but I have (somehow) seem both during the same replication steps, so the issue is the same.
|
Was on 0.6.1, didn't see new release 0.6.2, still replicating in 0.6.2, although now it is only thrown when "Current Job" is a selected column, or there is something inconsistent happening here. Regardless, issue is consistently replicable by selecting "Current Job" column, pausing the game, using DevTool "Tool: Down" on a pawn, then opening Numbers. Not sure if there is another subtly different bug lurking in this same comment chain, but I couldn't find enough of a difference to warrant two open tickets. |
[Bug] Occasionally, Window Fails to Fill, Spamming Stack Trace Instead
When it happens, the main view renders only a couple pawns (presumably until it hits the error row) and then suddenly renders no more pawns.
It happens on the GUI thread, so it spams the below stack trace error a bajillion times per second until the window is closed.
The text was updated successfully, but these errors were encountered: