From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30265] New: r600g: potential memory leak
Date: Sun, 19 Sep 2010 08:10:15 -0700 (PDT) [thread overview]
Message-ID: <bug-30265-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30265
Summary: r600g: potential memory leak
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: nikai@nikai.net
Created an attachment (id=38798)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38798)
(r600g) Output of valgrind --trace-children=yes --leak-check=full glxgears
Shortly running glxgears in valgrind with r600g:
LEAK SUMMARY:
definitely lost: 4,414,144 bytes in 236 blocks
With r600c, there's a lot less loss output.
System environment:
-- system architecture: amd64
-- Linux distribution: Gentoo
-- GPU: RS780G
-- Model: ATI Radeon HD 3200
-- Display connector: VGA
-- xf86-video-ati: b90cb61ccb0f4f80e0627141f223354a9371d47d
-- xserver: 1.9.0
-- mesa: e4513e7fb96c6336d8c7fcdadfaddb6b335a736e
-- drm: 7ec9a1effa4f551897f91f3b017723a8adf011d9
-- kernel: 2.6.36-rc4-00166-g151b6a5
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-19 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 15:10 bugzilla-daemon [this message]
2010-09-19 15:12 ` [Bug 30265] r600g: potential memory leak bugzilla-daemon
2010-10-01 11:34 ` 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-30265-502@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