Comment 9 for bug 1824587

This may be one of those corner cases where wxLogDebug would be an acceptable albeit less than ideal solution. I'm somewhat surprised that the wx folks don't suppress the event queue and prevent any further paint events when an assertion is raised. This would prevent the crash. I wonder if this was due to a bug in the assertion handler that has been fixed. Has anyone tried an assert here to see if it still crashes? Maybe the comment is out of date. The problem with wxLogDebug is that you will not see the issue unless you are looking at the debug output for an issue. It seems to me that assert would be the correct way to get a developers attention that they mucked up something.