From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 104340] New: Memory leak with GEM objects
Date: Tue, 19 Dec 2017 18:53:31 +0000 [thread overview]
Message-ID: <bug-104340-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104340
Bug ID: 104340
Summary: Memory leak with GEM objects
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: sgilles-8yXg+M/94Z32fBVCVOL8/A@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 136291
--> https://bugs.freedesktop.org/attachment.cgi?id=136291&action=edit
dmesg (up to last nouveau messages)
I have a gk106, current versions of libdrm, mesa, kernel (observed both with
-mainline and https://github.com/skeggsb/linux branch linux-4.15 as of a few
minutes ago), and there appears to be a memory leak with nouveau that eats up
about .5 GB every day. Killing X does nothing.
Attached is output of dmesg from the most recent boot of this machine. I've
also attached (in case it matters) dumps of /proc/meminfo and output of slabtop
after I ran X for about two weeks, then exited and killed all major daemons.
More importantly, I've attached a few hundred lines of
/sys/kernel/debug/kmemleak (from the most recent boot). After the first few
entries, they all start looking the same (except for the address and age).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3018 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-12-19 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 18:53 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-104340-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-12-19 18:54 ` [Bug 104340] Memory leak with GEM objects bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 22:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-19 23:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-104340-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.