All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109389] memory leak in `amdgpu_bo_create()`
Date: Tue, 03 Sep 2019 21:31:08 +0000	[thread overview]
Message-ID: <bug-109389-502-h7ZPccCU0U@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109389-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1258 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109389

Czcibor Bohusz-Dobosz <czbd@o2.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #145256|0                           |1
        is obsolete|                            |

--- Comment #6 from Czcibor Bohusz-Dobosz <czbd@o2.pl> ---
Created attachment 145257
  --> https://bugs.freedesktop.org/attachment.cgi?id=145257&action=edit
Galactic Civilizations III memleak log with DXVK

Apologies, looks like I had forgotten to update the methodology in several
places of the DXVK memleak log - this one should be much more accurate.

The updated methodology had however, to my understanding, showcased something
that I had not expected: apparently, the memory allocated by amdgpu_bo_create()
does not actually accumulate in a linear fashion, instead, it seems like it is
replaced the second time the game is launched. Because of that, there is a
chance that more than the 65 megabytes were actually unavailable after the test
without DXVK, perhaps a sum of all the amdgpu_bo_create() calls' allocations.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2706 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-09-03 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 21:11 [Bug 109389] memory leak in `amdgpu_bo_create()` bugzilla-daemon
2019-01-18 21:13 ` bugzilla-daemon
2019-01-19  1:16 ` bugzilla-daemon
2019-01-25 16:19 ` bugzilla-daemon
2019-02-12 15:05 ` bugzilla-daemon
2019-09-03 20:41 ` bugzilla-daemon
2019-09-03 20:49 ` bugzilla-daemon
2019-09-03 20:52 ` bugzilla-daemon
2019-09-03 21:31 ` bugzilla-daemon [this message]
2019-09-06 21:14 ` bugzilla-daemon
2019-09-06 21:16 ` bugzilla-daemon
2019-10-15 18:33 ` bugzilla-daemon
2019-11-19  9:11 ` 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-109389-502-h7ZPccCU0U@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.