Can you try with fewer state files? The memory leaks should still be visible in
the valgrind output.

Also, it would be better if you can exit VisIt cleanly instead of killing it,
otherwise valgrind might incorrectly report memory as leaked which is normally
freed correctly.