https://bugs.freedesktop.org/show_bug.cgi?id=91889
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #29 from Rokas Kupstys ---
I noticed this as well. It started happening after i upgraded my gpu to AMD
rx580 and started using amdgpu driver. Could this be amdgpu issue?
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #28 from Krzysztof A. Sobiecki ---
So there was additional trace file hidden in a subfolder:
Main:
https://drive.google.com/file/d/0B3J0Mg89izcbYnpzVjhSeVRmNEk/view?usp=sharing
Hidden one:
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #27 from Albert Freeman ---
(In reply to Krzysztof A. Sobiecki from comment #26)
> Trace from wayland/Xwayland:
> https://drive.google.com/file/d/0B3J0Mg89izcbR1BHWXEwREJhY00/view?usp=sharing
>
> It shows
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #26 from Krzysztof A. Sobiecki ---
Trace from wayland/Xwayland:
https://drive.google.com/file/d/0B3J0Mg89izcbR1BHWXEwREJhY00/view?usp=sharing
It shows only dark screen in menu.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #24 from Albert Freeman ---
Yep, you are absolutely right, I just walked through every single gl call in
the application (skipping redundant frames and shader compilation). The entire
UI is drawn outside
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #25 from Albert Freeman ---
Correction: I didn't walk through every call in the application, only util I
realised what was happening with the UI.
--
You are receiving this mail because:
You are the QA
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #21 from Eirik Byrkjeflot Anonsen ---
(In reply to Krzysztof A. Sobiecki from comment #20)
> (In reply to Michel Dänzer from comment #18)
> > (In reply to Krzysztof A. Sobiecki from comment #14)
> > > So how
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #23 from Eirik Byrkjeflot Anonsen ---
(In reply to almos from comment #22)
> (In reply to Eirik Byrkjeflot Anonsen from comment #21)
> > > No matter what they shouldn't be able to get that data. I'm starting to
> >
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #22 from almos ---
(In reply to Eirik Byrkjeflot Anonsen from comment #21)
> > No matter what they shouldn't be able to get that data. I'm starting to
> > think if it's possible to grab that data with OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #18 from Michel Dänzer ---
(In reply to Krzysztof A. Sobiecki from comment #14)
> So how glTexImage2D gets wrong data?
The data passed to glTexImage2D is controlled by the application. The question
is where it's
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #19 from Krzysztof A. Sobiecki ---
(In reply to Michel Dänzer from comment #18)
> (In reply to Krzysztof A. Sobiecki from comment #14)
> > So how glTexImage2D gets wrong data?
>
> The data passed to glTexImage2D is
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #20 from Krzysztof A. Sobiecki ---
(In reply to Michel Dänzer from comment #18)
> (In reply to Krzysztof A. Sobiecki from comment #14)
> > So how glTexImage2D gets wrong data?
>
> The data passed to glTexImage2D is
https://bugs.freedesktop.org/show_bug.cgi?id=91889
Krzysztof A. Sobiecki changed:
What|Removed |Added
Attachment #118228|text/plain |image/png
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #16 from Krzysztof A. Sobiecki ---
Created attachment 118228
--> https://bugs.freedesktop.org/attachment.cgi?id=118228=edit
Correct framebuffer
--
You are receiving this mail because:
You are the QA Contact for
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #17 from Krzysztof A. Sobiecki ---
Created attachment 118229
--> https://bugs.freedesktop.org/attachment.cgi?id=118229=edit
Faulty framebuffer
--
You are receiving this mail because:
You are the QA Contact for
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #15 from Krzysztof A. Sobiecki ---
Created attachment 118227
--> https://bugs.freedesktop.org/attachment.cgi?id=118227=edit
A texture that breaks things
This is a texture that is written over correct framebuffer
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #14 from Krzysztof A. Sobiecki ---
So I was looking trough PA.2.trace in qapitrace and I found that in frame 3001
it somehow corrupts framebuffer
So it happens like that:
glTexImage2D(GL_TEXTURE_2D,, binary
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #13 from Albert Freeman ---
Well the warning/error messages are the same in both traces so it can't be
them.
Possible workaround:
{
wget -O - https://github.com/pamods/pamm-atom/raw/stable/install.sh |
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #5 from Albert Freeman ---
The GPU has its own physical ram that is managed with a completely different
system than system ram.
There are actually two issues here. One is the bug in the game causing
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #7 from Albert Freeman ---
*with the replay
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #8 from Albert Freeman ---
Created attachment 118184
--> https://bugs.freedesktop.org/attachment.cgi?id=118184=edit
Warning messages from apitrace replay before "export
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #9 from Albert Freeman ---
When I said "bug in the game", I meant "bug with the game".
Can you upload another trace (please try to reproduce the bug as fast as
possible (since parts of the trace can't be
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #11 from Albert Freeman ---
Does the screenshot you posted look [around about]/exactly the same as actually
playing the game does?
--
You are receiving this mail because:
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #10 from Krzysztof A. Sobiecki ---
Of course I will make another trace. But it looks like corrupted textures were
saved into a trace.
Like part of memory(vram) is used as texture, it should be initialized to some
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #12 from Krzysztof A. Sobiecki ---
(In reply to Albert Freeman from comment #11)
> Does the screenshot you posted look [around about]/exactly the same as
> actually playing the game does?
Yes it does
I have made
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #4 from Krzysztof A. Sobiecki ---
It's about one process accessing graphic memory of other process, how it's even
possible. Doesn't kernel some kind of memory management facility to prevent
that?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #2 from Krzysztof A. Sobiecki ---
Apitrace:
https://drive.google.com/file/d/0B3J0Mg89izcbMVgzMDdWYkxoY3M/view?usp=sharing
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #3 from Albert Freeman ---
The mesa developers are well aware of this and see it all the time in a myriad
of different environments. It isn't only a problem in mesa, but also in other
parts of the linux
https://bugs.freedesktop.org/show_bug.cgi?id=91889
Bug ID: 91889
Summary: Planetary Anihilation: Titans display content of other
processes buffers
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=91889
Krzysztof A. Sobiecki changed:
What|Removed |Added
Priority|medium |highest
--
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #1 from Krzysztof A. Sobiecki ---
My specs:
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.0-devel
VGA compatible
32 matches
Mail list logo