Debug Assertion Dialog - Abort / Retry / Ignore¶
Summary¶
A Windows debug/assertion dialog with Abort / Retry / Ignore means the Flair build has hit code that should not execute. Retry may continue into the fault and crash; Abort exits; Ignore is usually the least disruptive choice, but the job should be saved immediately to a new file and a bug report sent with reproduction steps.
Symptoms¶
- Dialog appears with Abort / Retry / Ignore
- Flair may continue running while the dialog is open
- Triggered by editing/rippling keyframes in at least one reported job
- Repeatable in a specific job but not necessarily all jobs
Stable ID¶
ISSUE-CRASH-010
First Reported¶
2023-03-16 - image-defined error dialog in chat.
Software Environment¶
Both, but likely build-specific. The chat describes a program compiled in debug mode hitting a bug/assertion.
Community Solutions¶
[CONFIRMED] 2023-03-16 - User: David Goldsmith¶
The dialog appears when a debug build hits a bug/assertion. Retry likely executes the bug and may crash; Abort kills the app. The app is effectively in a limbo state while the dialog is open.
confidence_score: 0.84
[CONFIRMED] 2023-03-17 - User: Simon Wakley¶
Ignore is usually best, but save the job. Immediately send a bug report and include the job plus exact steps that cause the issue. Note whether it is repeatable and whether it occurs when typing numbers or using ripple-through operators like -, +, or *.
confidence_score: 0.88
Related Media¶
Media Text / Description¶
- Media 1: 2023-03-16 — ~ Radu Stefan Fulga: WhatsApp video showing Flair debug dialog with Abort, Retry, and Ignore buttons while adjusting keyframes.
WhatsApp Excerpts¶
- 2023-03-16 21:56 - ~ Radu Stefan Fulga: Hi guys, when I adjust keyframes I sometimes get this strange message. If I click abort or retry, Flair crashes, if I click ignore, it seems to continue working. Anybody know what this is?
- 2023-03-16 22:31 - ~ Niko: Good question
- 2023-03-16 23:46 - David Goldsmith: This message pops up when the program was compiled in debug mode and hits a bug, which might crash the application otherwise. Since the way this works is that the code behind this message fires when the app does something that it shouldn’t, it’s able to stop the bug from executing while it waits for you to click a button. If you click retry, it executes the bug (probably crashing). Abort kills the app. So I believe you are in a sort of limbo while that window is up and the app still running. I...
- 2023-03-17 02:21 - ~ Simon Wakley: Please immediately send a bug report and include the job and exactly what you do that causes the issue. Is it repeatable? Most likely when you type the number Flair is trying to update a window that doesn’t exist. Are you typing just the number of using the “ripple through” with a -+* etc?
Related Issues¶
- See also: Flair Crashes Cancelling Speed Warnings — Move Lost From Current Job
- See also: Flair Crashes Opening Graph View — Axis Type Set to 'Unused