https://bugs.freedesktop.org/show_bug.cgi?id=83022
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #6 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 inc
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #5 from pavol at klacansky.com ---
I tried to run it with valgrind and there are so many errors and it just
crashed whole system (I mean disk IO was so high I had to press shutdown
button, I do not get this, as I had no swap enabled).
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #4 from pavol at klacansky.com ---
Created attachment 105221
--> https://bugs.freedesktop.org/attachment.cgi?id=105221&action=edit
glxinfo
--
You are receiving this mail because:
You are the assignee for the bug.
-- nex
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #3 from pavol at klacansky.com ---
Created attachment 105220
--> https://bugs.freedesktop.org/attachment.cgi?id=105220&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #2 from pavol at klacansky.com ---
Created attachment 105219
--> https://bugs.freedesktop.org/attachment.cgi?id=105219&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=83022
--- Comment #1 from Michel D?nzer ---
First of all, please attach /var/log/Xorg.0.log and the output of dmesg and
glxinfo.
The output from running the app with valgrind --leak-check=full (preferably
with debugging symbols available for r600_dri.
