From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jason Detring <jason.detring@navico.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: Memory leak in drm/i915?
Date: Wed, 03 Nov 2010 19:05:40 +0000 [thread overview]
Message-ID: <849307$a89e5p@azsmga001.ch.intel.com> (raw)
In-Reply-To: <BEE90EB7BDBD334E9FC58E1629B5CBCA01867F2E@exch01-tulus.MARINE.NET.INT>
On Wed, 3 Nov 2010 13:31:58 -0500, "Jason Detring" <jason.detring@navico.com> wrote:
> App running for 60 minutes (we've just started swapping):
>
> /sys/kernel/debug/dri/0/i915_gem_objects
> 514 objects
> 390938624 object bytes
> 3 pinned
> 7471104 pin bytes
> 12 mappable objects in gtt
> 10108928 mappable gtt bytes
> 124223488 mappable gtt used bytes
> 125960192 mappable gtt total
> 206 objects in gtt
> 124223488 gtt bytes
> 125960192 gtt total
Looks like an ordinary userspace bo leak. Now you want to start
instrumenting textures and making sure they are all accounted for. Equally
the bug may be in mesa leaking references.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-03 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 15:26 Memory leak in drm/i915? Jason Detring
2010-11-03 16:02 ` Chris Wilson
2010-11-03 18:31 ` Jason Detring
2010-11-03 19:05 ` Chris Wilson [this message]
2010-11-08 15:27 ` Jason Detring
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='849307$a89e5p@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason.detring@navico.com \
/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