From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75732] [r600g] Memory leak with celestia, RV790
Date: Tue, 04 Mar 2014 04:11:49 +0000 [thread overview]
Message-ID: <bug-75732-502-dIlSfWZ6d4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75732-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 576 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75732
--- Comment #2 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #1)
> Having recompiled the current Mesa from git, it looks as if
> radeon_winsys_destroy() in src/gallium/winsys/radeon/drm/radeon_drm_winsys.c
> is not being called on exit.
That only explains 352 leaked bytes though, over the whole lifetime of the
celestia process.
Please describe the problem in more detail. Why do you think there is a leak?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1428 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:[~2014-03-04 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 23:26 [Bug 75732] New: Memory leak with celestia bugzilla-daemon
2014-03-03 23:26 ` [Bug 75732] [r600g] Memory leak with celestia, RV790 bugzilla-daemon
2014-03-04 0:43 ` bugzilla-daemon
2014-03-04 4:11 ` bugzilla-daemon [this message]
2014-03-04 8:53 ` bugzilla-daemon
2014-03-04 8:57 ` bugzilla-daemon
2014-03-05 2:47 ` bugzilla-daemon
2014-03-05 8:48 ` bugzilla-daemon
2014-03-05 14:31 ` bugzilla-daemon
2019-09-18 19:15 ` 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-75732-502-dIlSfWZ6d4@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