https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #6 from Michel D?nzer <michel at daenzer.net> --- 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. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140826/1c8570d8/attachment.html>
