Comment # 6
on bug 83022
from Michel Dänzer
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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
