dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 115781] New: Hyper-V video driver leaking memory
Date: Sat, 02 Apr 2016 04:53:51 +0000	[thread overview]
Message-ID: <bug-115781-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=115781

            Bug ID: 115781
           Summary: Hyper-V video driver leaking memory
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.4.5-1
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: feduzi@mailinator.com
        Regression: No

After some testing seems like hyper-v video driver is leaking memory.

The setup:
Host OS: Windows 10 + Hyper-V
Guest OS: a linux distro

Steps to reproduce (archlinux example):
1. Setup a minimal system (and xorg-server, xorg-server-utils, xterm)
2. Launch "top" and wait. (I waited for an hour, and have seen no changes in
memory allocation)
3. Use "startx" to launch basic X11 session.
4. Launch "top" and wait. (It takes 5-10 minutes for me, for memory to be
mostly occupied, about 20% is left)

Steps to reproduce (ubuntu server example):
1. Setup a minimal system (and xorg, xterm)
2. Launch "top" and wait. (I waited for an hour, and have seen no changes in
memory allocation)
3. Use "startx" to launch basic X11 session.
4. Launch "top" and wait. (It takes 5-10 minutes for me, for memory to be
mostly occupied, about 15% is left)

As seen from the 2 examples above, we have an issue across different distros.
Also I've set up the same 2 distros on VirtualBox VMs and had no issues with
memory allocation, which point into Hyper-V direction.
As seen previously the issue is not occurring until X11 is not launched, which
points into display-related direction.
Also to note, I tried to use top/htop tools to pinpoint a program, which leaks
memory. But the most used memory percentage is 0.3 at the time when 80% of RAM
is used, which points into non-program direction (I assumed driver).

Thanks.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-04-02  4:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02  4:53 bugzilla-daemon [this message]
2016-04-02  5:31 ` [Bug 115781] Hyper-V video driver leaking memory 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-115781-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox