All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26708] New: libdrm-intel leaks memory when resizing window
Date: Mon, 22 Feb 2010 13:47:25 -0800 (PST)	[thread overview]
Message-ID: <bug-26708-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: libdrm-intel leaks memory when resizing window
           Product: DRI
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libdrm
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: penma.bfdo@penma.de


At least the DRM/Intel module continues to suck up memory just by resizing the
window. This would be acceptable behaviour if it wouldn't continue to grow on
and on, as it happens for software rendering.

This can not only be reproduced with a (potentially buggy) selfwritten test
program but also with the glxdemo.c program from Mesa.

To reproduce, start the test program and make the window smaller, and larger,
and smaller again quite wildly and often (10-30 seconds or so).

What happens if you start it with LIBGL_ALWAYS_SOFTWARE=1: Memory usage goes up
to about 10M and stays there.

What happens if you start it without that option set (DRM/Intel): Memory usage
continues to grow with every resize operation even when the window size is only
changed around 100x100 +-5px.

Excerpt from Valgrind output (it had lots of those):

 ==11088== 3,244,032 bytes in 99 blocks are still reachable in loss record 331
of 331
 ==11088==    at 0x4C221A7: malloc (vg_replace_malloc.c:195)
 ==11088==    by 0x7B3A822: ??? (in /usr/lib/libdrm_intel.so.1.0.0)
 ==11088==    by 0x74B2344: ??? (in /usr/lib/dri/i965_dri.so)
 ==11088==    by 0x74B41AD: brw_validate_state (in /usr/lib/dri/i965_dri.so)
 ==11088==    by 0x74A6DBD: brw_draw_prims (in /usr/lib/dri/i965_dri.so)
 ==11088==    by 0x75641A4: vbo_exec_vtx_flush (in /usr/lib/dri/i965_dri.so)
 ==11088==    by 0x7560154: vbo_exec_FlushVertices_internal (in
/usr/lib/dri/i965_dri.so)
 ==11088==    by 0x7560221: vbo_exec_FlushVertices (in
/usr/lib/dri/i965_dri.so)
 ==11088==    by 0x74DB15D: _mesa_Flush (in /usr/lib/dri/i965_dri.so)
 ==11088==    by 0x4E4C2B1: glXSwapBuffers (in /usr/lib/libGL.so.1.2)

One test run got 23 MiB of still accessible memory all from libdrm. I don't
think it's used for anything useful, if not because of the size, then because
of the fact the software renderer does not leak.


-- 
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-22 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 21:47 bugzilla-daemon [this message]
2010-02-24  7:51 ` [Bug 26708] libdrm-intel leaks memory when resizing window bugzilla-daemon
2010-02-24 14:44 ` 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=bug-26708-502@http.bugs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.