From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98693] Mad Max: Long lags when VRAM full
Date: Sat, 12 Nov 2016 00:46:58 +0000 [thread overview]
Message-ID: <bug-98693-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1213 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98693
Bug ID: 98693
Summary: Mad Max: Long lags when VRAM full
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: jani.karkkainen@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
I get random lagging when playing the recently released Mad Max. Every once in
a while, the game freezes completely, and gets back to the game after an
arbitrary amount of seconds, anywhere from 2 to 35.
With GALLIUM_HUD, and noticed that the lags appear to precede the VRAM slowly
ramping up to full, and then I get this huge lag, and then VRAM usage is a lot
lower (eg. from 1GB to ~600MB).
I found this possibly related news item from a couple of months back:
https://www.gamingonlinux.com/articles/a-reason-for-poor-performance-on-amd-plus-mesa-has-been-found-and-a-patch-is-in-progress.7873
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2718 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 reply other threads:[~2016-11-12 0:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 0:46 bugzilla-daemon [this message]
2016-11-16 8:46 ` [Bug 98693] Mad Max: Long lags when VRAM full bugzilla-daemon
2016-11-17 3:52 ` bugzilla-daemon
2016-11-17 5:50 ` bugzilla-daemon
2016-11-17 10:24 ` bugzilla-daemon
2016-11-17 13:37 ` bugzilla-daemon
2017-03-12 13:24 ` bugzilla-daemon
2019-07-04 2:36 ` 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-98693-502@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.