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, 15 Oct 2019 18:33:18 +0000	[thread overview]
Message-ID: <bug-109389-502-EUFDGE4JZE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109389-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Czcibor Bohusz-Dobosz <czbd@o2.pl> ---
As far as I'm able to test after bcc memleak decided to randomly stop working
on my machine, the leak is gone with Linux 5.3.6-arch1-1-ARCH and Mesa 19.2.1.

Great thanks to whoever managed to resolve this crippling issue!

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

[-- Attachment #1.2: Type: text/html, Size: 1175 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-10-15 18:33 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
2019-09-06 21:14 ` bugzilla-daemon
2019-09-06 21:16 ` bugzilla-daemon
2019-10-15 18:33 ` bugzilla-daemon [this message]
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-EUFDGE4JZE@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.