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: Thu, 21 Jul 2016 04:10:50 +0000 [thread overview]
Message-ID: <bug-97003-502-RRJfkJYsyI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97003-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97003
--- Comment #4 from kudahkukarek@gmail.com ---
(In reply to Michel Dänzer from comment #3)
> valgrind doesn't understand some (not very) recent AMD specific instructions
> yet. I build everything with -march=amdfam10 -mtune=native to avoid this.
Ok, I'll recompile wine and try again.
> Right, but video memory leaks are usually accompanied by corresponding
> system memory leaks, which can be caught by valgrind.
True, the game does noticeably leak system memory (1.5+ GiB footprint with
precompiled shaders vs 500 MB with mono)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1614 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:[~2016-07-21 4:10 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 [this message]
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
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-RRJfkJYsyI@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.