From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97003] [d3dadapter+radeonsi] Dragon's Dogma: video memory leak with precompiled shaders
Date: Tue, 14 Feb 2017 02:53:10 +0000 [thread overview]
Message-ID: <bug-97003-502-tpqTgrdoId@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97003-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97003
--- Comment #8 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Roland Scheidegger from comment #7)
> 0x36 looks like a segment override (ss segment) prefix (0x89 would be a
> mov), so nothing new.
> This looks like a valgrind bug to me:
> https://bugs.kde.org/show_bug.cgi?id=344139 which seems old, in particular
> no updates since over a year (and specifically mentions wine is using such
> segment override prefixes).
Looks like a fix has been merged into valgringd git.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1620 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-14 2:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:33 [Bug 97003] [d3dadapter+radeonsi] Dragon's Dogma: video memory leak with precompiled shaders bugzilla-daemon
2016-07-20 8:38 ` bugzilla-daemon
2016-07-20 23:35 ` bugzilla-daemon
2016-07-21 2:07 ` bugzilla-daemon
2016-07-21 4:10 ` bugzilla-daemon
2016-07-22 9:08 ` bugzilla-daemon
2016-07-22 9:16 ` bugzilla-daemon
2016-07-23 1:07 ` bugzilla-daemon
2017-02-14 2:53 ` bugzilla-daemon [this message]
2018-08-31 6:30 ` 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-97003-502-tpqTgrdoId@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox