All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200387] amdgpu uses unusually high memory
Date: Tue, 03 Jul 2018 16:31:47 +0000	[thread overview]
Message-ID: <bug-200387-2300-OHukwrIN7e@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200387-2300@https.bugzilla.kernel.org/>

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

--- Comment #22 from phoenix (felix@feldspaten.org) ---
Apperently it's not that easy to attach valgrind to any Steam game, so I'm
going the suggested approach of trying it out using different Kernel version.

Interestingly I could observe similar behaviour in Stardew Valley but not in
Kerbal Space program, as the following attached statm shows:


## /proc/$ID/statm for Stardew Valley (Similar problem see the data segment)
# statm for 4917 on 4.17.3
978381 424915 23927 849 0 449695 0
# statm for 4370 on 4.4.0
979917 418188 23774 849 0 874146 0

## /proc/$ID/statm for Kerbal Space Program (Problem does not occur)
# statm of 5419 on 4.4.0
532753 381415 19974 7863 0 446822 0
# statm of on 4.17.3
529142 389210 19754 7863 0 441862 0

I'm investigating using different Kernel versions and maybe I'm able to write a
simple OpenGL program that triggers the problem.

-- 
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

  parent reply	other threads:[~2018-07-03 16:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 15:54 [Bug 200387] New: amdgpu uses unusually high memory bugzilla-daemon
2018-07-02  3:34 ` [Bug 200387] " bugzilla-daemon
2018-07-02 10:13 ` bugzilla-daemon
2018-07-02 10:55 ` bugzilla-daemon
2018-07-02 15:14 ` bugzilla-daemon
2018-07-02 15:14 ` bugzilla-daemon
2018-07-02 15:15 ` bugzilla-daemon
2018-07-02 15:15 ` bugzilla-daemon
2018-07-02 15:19 ` bugzilla-daemon
2018-07-02 15:19 ` bugzilla-daemon
2018-07-02 15:21 ` bugzilla-daemon
2018-07-02 15:39 ` bugzilla-daemon
2018-07-02 16:03 ` bugzilla-daemon
2018-07-02 16:29 ` bugzilla-daemon
2018-07-02 16:50 ` bugzilla-daemon
2018-07-02 20:40 ` bugzilla-daemon
2018-07-03  7:27 ` bugzilla-daemon
2018-07-03  7:42 ` bugzilla-daemon
2018-07-03  7:54 ` bugzilla-daemon
2018-07-03  7:55 ` bugzilla-daemon
2018-07-03  8:08 ` bugzilla-daemon
2018-07-03  8:11 ` bugzilla-daemon
2018-07-03 16:31 ` bugzilla-daemon [this message]
2018-07-03 16:45 ` bugzilla-daemon
2018-07-03 17:40 ` bugzilla-daemon
2018-07-03 19:16 ` bugzilla-daemon
2018-07-04  8:01 ` bugzilla-daemon
2018-07-04  8:40 ` bugzilla-daemon
2018-07-04 10:00 ` bugzilla-daemon
2018-07-05 17:09 ` bugzilla-daemon
2018-07-08 12:57 ` 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-200387-2300-OHukwrIN7e@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 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.