Comment 7 for bug 1284391

Note also that if "top" is running in another window when the toxic file opens the CPU usage never settles down. Normally in Inkscape when nothing is happening the CPU usage drops to something small, <1% typically. Here it stayed above 70%.

Finally managed to get a controlled exit from within valgrind by:

valgrind -v --leak-check=yes --leak-resolution=high --num-callers=15 --show-reachable=yes --suppressions=./wcslen_sse2.supp src/inkscape --file /tmp/td_test1.pdf >/tmp/vgA.log 2>&1

then when it finally opened the main window, click once on a bare patch near the bottom and enter ^Q. There are a variety of access violations and "conditional jump or move depends on uninitialized values(s)". Relevant part of the valgrind log attached. That is followed by a typical insanely long list of memory warnings - too much stuff in there to figure out if there is anything new related to this bug.