I then ran
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log evince manual.dvi
Evince started slower now (expected because of valgrind and the env variables).
Evince no longer crashed, and, even more, after closing evince, calling evince on the same manual.dvi file DID NOT lead to a crash.
There's some kind of heisenbug here.
I ran evince on http:// paultaylor. eu/diagrams/ manual. dvi (downloaded it beforehand) and it crashed.
I then ran SLICE=always- malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file= valgrind. log evince manual.dvi
G_
Evince started slower now (expected because of valgrind and the env variables).
Evince no longer crashed, and, even more, after closing evince, calling evince on the same manual.dvi file DID NOT lead to a crash.
So, to make it clear, after making the check with valgrind, evince no longer crashed while loading manual.dvi from http:// paultaylor. eu/diagrams/ manual. dvi