On Nov 15, 2008, at 4:38 AM, Diederik van Lierop wrote:

- Why was this only a problem on Windows? No one has been able to reproduce this on Linux. My hypothesis is that both platforms suffered from the same bug, but that Inkscape simply didn't die on Linux and kept running (on Windows Inkscape kept running too after the crash dialog, but only for a few seconds). Keeping Inkscape running is obviously good from a user perspective. However, it didn't even produce a warning on Linux, which is bad from a developers point of view. An out-of-bounds error should be screamed out loud!

This can often be caught by using valgrind.

_INKSCAPE_GC=disable valgrind --tool=memcheck inkscape