From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91982] [radeonsi] fs leak in get_radeon_bo() Date: Mon, 14 Sep 2015 07:39:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1940932108==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E7E0B6E7CC for ; Mon, 14 Sep 2015 00:39:38 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1940932108== Content-Type: multipart/alternative; boundary="1442216378.E0bCdDC0.14199"; charset="UTF-8" --1442216378.E0bCdDC0.14199 Date: Mon, 14 Sep 2015 07:39:38 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=91982 iive changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ikalvachev@gmail.com --- Comment #5 from iive --- 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. --1442216378.E0bCdDC0.14199 Date: Mon, 14 Sep 2015 07:39:38 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" changed bug 91982
What Removed Added
CC   ikalvachev@gmail.com

Comment # 5 on bug 91982 from 
Created attachment 118258 [details]
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.
--1442216378.E0bCdDC0.14199-- --===============1940932108== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1940932108==--