dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26708] libdrm-intel leaks memory when resizing window
Date: Tue, 23 Feb 2010 23:51:32 -0800 (PST)	[thread overview]
Message-ID: <20100224075133.3DB311300E4@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26708-502@http.bugs.freedesktop.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=26708





--- Comment #1 from Lars S <penma.bfdo@penma.de>  2010-02-23 23:51:32 PST ---
Created an attachment (id=33521)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=33521)
full valgrind output of a test run

For completeness I have attached a more complete Valgrind output file of a test
run with the glxdemo program.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  reply	other threads:[~2010-02-24  7:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 21:47 [Bug 26708] New: libdrm-intel leaks memory when resizing window bugzilla-daemon
2010-02-24  7:51 ` bugzilla-daemon [this message]
2010-02-24 14:44 ` [Bug 26708] " bugzilla-daemon
2010-02-24 16:28 ` bugzilla-daemon
2010-02-24 16:29 ` bugzilla-daemon
2010-02-24 16:43 ` bugzilla-daemon
2010-02-24 18:29 ` bugzilla-daemon
2010-02-24 18:30 ` bugzilla-daemon
2019-09-24 17:08 ` 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=20100224075133.3DB311300E4@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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