From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65968] New: Massive memory corruption in Planetary Annihilation Alpha
Date: Thu, 20 Jun 2013 12:55:22 +0000 [thread overview]
Message-ID: <bug-65968-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2331 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65968
Priority: medium
Bug ID: 65968
Assignee: dri-devel@lists.freedesktop.org
Summary: Massive memory corruption in Planetary Annihilation
Alpha
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: andreas.ringlstetter@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/r300
Product: Mesa
Created attachment 81105
--> https://bugs.freedesktop.org/attachment.cgi?id=81105&action=edit
Example of corruption in PA. The skybox texture has been completely
overwritten, partly with textures from other programms, corruption in other
textures is already starting.
Using the R300 driver (git version from 2013-06-19) on a Mobility Radeon X1400
(128MB dedicated ???), I get massive memory corruption which can be seen in the
attached screenshot when running the Planetary Annihilation Alpha.
The game makes use of virtual texturing, thats means a mega texture which won't
possibly fit in the RAM in one piece.
However, it appears like textures which are NOT part of the mega texture have
been mapped into the same address space. I could see other textures, and even
bitmaps from other applications.
In the screenshot, there are large grey stripes for example, however there is
no such texture in the game. The color does match the color of the window
border though. Performing further tests, I even managed to get parts of album
covers from Banshee into PA.
This issue is not only limited to Planetary Annihilation though and the
corruption also works other way around, where applications overwrite the
bitmaps of other applications.
The effects of the corruption are clearly visible in PA due to the large
textures. They are not deterministic, but appear very reliable, most likely due
to the high memory usage.
Using other applications which frequently allocate new textures (like Banshee
with album covers) speeds up the corruption and makes it even visible in other
applications like Firefox, Cinnamon etc., although not reliable.
Attached are:
Screenshot of corruption
Xorg-log
glxinfo output
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4061 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-06-20 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:55 bugzilla-daemon [this message]
2013-06-20 12:56 ` [Bug 65968] Massive memory corruption in Planetary Annihilation Alpha bugzilla-daemon
2013-06-20 12:56 ` bugzilla-daemon
2013-06-20 12:58 ` bugzilla-daemon
2013-06-20 13:10 ` bugzilla-daemon
2013-06-20 13:57 ` bugzilla-daemon
2013-06-22 11:47 ` bugzilla-daemon
2013-06-22 12:34 ` bugzilla-daemon
2017-02-10 3:04 ` bugzilla-daemon
2017-02-10 3:11 ` bugzilla-daemon
2017-02-10 3:51 ` bugzilla-daemon
2017-02-14 5:21 ` bugzilla-daemon
2017-02-14 12:03 ` bugzilla-daemon
2017-02-14 17:50 ` 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-65968-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 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).