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 16:02:26 +0000 [thread overview]
Message-ID: <849307$a86oqb@azsmga001.ch.intel.com> (raw)
In-Reply-To: <BEE90EB7BDBD334E9FC58E1629B5CBCA01867E48@exch01-tulus.MARINE.NET.INT>
On Wed, 3 Nov 2010 10:26:11 -0500, "Jason Detring" <jason.detring@navico.com> wrote:
> The problem observed is that performing this switch seems to grow system
> cache usage by about 1.5 to 2 MB per iteration. This is unbounded, and
> will fill both free memory and swap in the course of a few hours when
> running our app in its demonstration cycle. At this point, the system
> becomes unresponsive, eventually dumping the user to a text-mode kernel
> panic message. Killing the app before the hang causes the system cache
> and swap to be cleared on an intel-drm-next kernel, but not in the -rc3
> kernel (see software stacks later in this message).
This suggests that the leak is connected with:
commit 31dfbc93923c0aaa0440b809f80ff2830c6a531a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Mon Sep 27 21:28:30 2010 +0100
drm: Prune GEM vma entries
Hook the GEM vm open/close ops into the generic drm vm open/close so
that the private vma entries are created and destroy appropriately.
Fixes the leak of the drm_vma_entries during the lifetime of the filp.
Can you monitor /sys/debug/dri/0/i915_gem_objects and /proc/slabinfo and
see where the memory is going?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-03 16:02 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 [this message]
2010-11-03 18:31 ` Jason Detring
2010-11-03 19:05 ` Chris Wilson
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$a86oqb@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