From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91982] [radeonsi] fs leak in get_radeon_bo()
Date: Mon, 14 Sep 2015 07:39:38 +0000 [thread overview]
Message-ID: <bug-91982-502-96aFiE6NBK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91982-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91982
iive <ikalvachev@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ikalvachev@gmail.com
--- Comment #5 from iive <ikalvachev@gmail.com> ---
Created attachment 118258
--> https://bugs.freedesktop.org/attachment.cgi?id=118258&action=edit
Valgrind trace of memory leaks in Mesa3D when compiling same shader over and
over. R600 Redwood variant.
You need to run valgrind with `--trace-children` to check something else than
apitrace itself. :)
I'm attaching log created with the following command:
`valgrind --log-file=mesa.memleak.r600.valgrind.txt --trace-children=yes
--leak-check=full --undef-value-errors=no --partial-loads-ok=yes
--freelist-vol=200000000 apitrace replay --loop -b bl2469.trace`
I didn't let it die from memory exhaustion, I pressed ESC and exited normally,
so the leaks in this log are definitely lost.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-14 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 19:03 [Bug 91982] [radeonsi] fs leak in get_radeon_bo() bugzilla-daemon
2015-09-11 19:04 ` bugzilla-daemon
2015-09-13 15:42 ` bugzilla-daemon
2015-09-14 1:40 ` bugzilla-daemon
2015-09-14 3:12 ` bugzilla-daemon
2015-09-14 7:39 ` bugzilla-daemon [this message]
2015-09-14 18:35 ` bugzilla-daemon
2015-09-14 21:44 ` bugzilla-daemon
2016-08-31 3:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-91982-502-96aFiE6NBK@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox