From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94726] [Tonga] ARK: Survival Evolved crashes on savegame load. Out of Memory
Date: Mon, 25 Apr 2016 08:46:31 +0000 [thread overview]
Message-ID: <bug-94726-502-u32Or616En@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94726-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 389 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94726
--- Comment #10 from Grigori Goronzy <greg@chown.ath.cx> ---
Maybe I'm naive here, but shouldn't it be possible to detect when we reach the
limit? Then we could unmap some buffers (preferably ones that haven't been
accessed for some time) only when it's needed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1196 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-04-25 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 20:13 [Bug 94726] [Tonga] ARK: Survival Evolved crashes on savegame load. Out of Memory bugzilla-daemon
2016-03-27 20:26 ` bugzilla-daemon
2016-03-28 7:48 ` bugzilla-daemon
2016-03-28 11:13 ` bugzilla-daemon
2016-04-09 17:56 ` bugzilla-daemon
2016-04-09 17:57 ` bugzilla-daemon
2016-04-13 16:04 ` bugzilla-daemon
2016-04-14 20:40 ` bugzilla-daemon
2016-04-15 0:09 ` bugzilla-daemon
2016-04-15 18:11 ` bugzilla-daemon
2016-04-25 8:46 ` bugzilla-daemon [this message]
2016-04-25 17:22 ` bugzilla-daemon
2016-10-07 19:11 ` bugzilla-daemon
2016-10-11 1: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-94726-502-u32Or616En@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;
as well as URLs for NNTP newsgroup(s).