Comment 34 for bug 1838448

I think we absolutely should enable all possible sanitizations and checks in all builds.

It's just pure luck that the bug is in vrml export and it's no big deal to ignore it. What if next time it will corrupt the project files? It's much better to "catch" that in a crash than silently ignore it.

KiCad doesn't have nearly enough automated test coverage so we rely heavily on user reports and there are not a lot of users running debug builds. I'm a dev and I only run debug build when I am triaging an issue because it's too slow for everyday use.

It's one thing to suppress gui library asserts because they are annoying and confusing in release build. But ignoring memory access violations can go very wrong very fast.