https://bugs.freedesktop.org/show_bug.cgi?id=74539
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #37 from Chris Rankin ---
Created attachment 98185
--> https://bugs.freedesktop.org/attachment.cgi?id=98185=edit
dmesg output with 3.14.2
Drat, I had hoped that this issue had been fixed.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #36 from Michel D?nzer ---
(In reply to comment #35)
> [...] it appears to be spinning uselessly here:
>
> 0x005732b4 in DRI2DrawableGone (p=0x1977780, id=1117838198) at
> dri2.c:382
> 382
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #35 from Chris Rankin ---
Created attachment 97584
--> https://bugs.freedesktop.org/attachment.cgi?id=97584=edit
Xorg backtrace when WoW fails to exit
The problem with Xorg happened again, so I logged in via another machine and
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #34 from Michel D?nzer ---
(In reply to comment #33)
> This is the Xorg.0.log file from an instance where I didn't get
> keyboard/mouse control back at all, and Xorg just chewed up 100% of one CPU
> instead.
DRICloseScreen is a DRI1
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #33 from Chris Rankin ---
Created attachment 97325
--> https://bugs.freedesktop.org/attachment.cgi?id=97325=edit
Xorg.0.log showing errors when exiting WoW
One of the other errors that I've come to associate (rightly or wrongly)
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #32 from Chris Rankin ---
(In reply to comment #31)
> It's not a bug fix, so I doubt it would be accepted.
Perhaps not, but possibly worth asking Mr Greg KH if he'd be prepared to
consider it anyway?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #31 from Marek Ol??k ---
It's not a bug fix, so I doubt it would be accepted.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #30 from Chris Rankin ---
(In reply to comment #29)
> With kernel 3.15, you can watch GPU memory usage by setting:
> GALLIUM_HUD=VRAM-usage,GTT-usage
Is this support sufficiently non-invasive to be backported to 3.14-stable?
--
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #29 from Marek Ol??k ---
With kernel 3.15, you can watch GPU memory usage by setting:
GALLIUM_HUD=VRAM-usage,GTT-usage
You should able to see if we leak GPU memory or not.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #28 from Chris Rankin ---
(In reply to comment #26)
> Does the patch from bug 74868 help?
Hmm, it hasn't OOM-ed yet. But one of the symptoms that I'd come to associate
with the memory problem was an increasing jerkiness in the game
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #27 from Chris Rankin ---
Thanks, I'll give it a try. Was Mesa leaking memory for *all* failed shaders,
or just failed geometry shaders?
> I tried booting up Diablo III a few days back to see the new geometry shaders
> in action on
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #26 from Michel D?nzer ---
Does the patch from bug 74868 help?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #25 from Chris Rankin ---
Created attachment 97051
--> https://bugs.freedesktop.org/attachment.cgi?id=97051=edit
dmesg output from 3.13.9
This memory leak is still present with 3.13.9 and HEAD
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #24 from Chris Rankin ---
Created attachment 95257
--> https://bugs.freedesktop.org/attachment.cgi?id=95257=edit
apitrace output for 32 bit WoW (8)
This is a less ambitious apitrace from 32 bit WoW. You can reconstruct the
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #23 from Chris Rankin ---
Created attachment 95256
--> https://bugs.freedesktop.org/attachment.cgi?id=95256=edit
apitrace output for 32 bit WoW (7)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #22 from Chris Rankin ---
Created attachment 95255
--> https://bugs.freedesktop.org/attachment.cgi?id=95255=edit
apitrace output for 32 bit WoW (6)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #21 from Chris Rankin ---
Created attachment 95254
--> https://bugs.freedesktop.org/attachment.cgi?id=95254=edit
apitrace output for 32 bit WoW (5)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #20 from Chris Rankin ---
Created attachment 95253
--> https://bugs.freedesktop.org/attachment.cgi?id=95253=edit
apitrace output for 32 bit WoW (4)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #19 from Chris Rankin ---
Created attachment 95252
--> https://bugs.freedesktop.org/attachment.cgi?id=95252=edit
apitrace output for 32 bit WoW (3)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #18 from Chris Rankin ---
Created attachment 95250
--> https://bugs.freedesktop.org/attachment.cgi?id=95250=edit
apitrace output for 32 bit WoW (2)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #17 from Chris Rankin ---
Created attachment 95249
--> https://bugs.freedesktop.org/attachment.cgi?id=95249=edit
apitrace output for 32 bit WoW (1)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #16 from Chris Rankin ---
The apitrace is 155,721 KB and so cannot be uploaded. Rather than break it into
> 50 fragments, does anyone have another location to upload it to please?
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #15 from Michel D?nzer ---
(In reply to comment #14)
> Actually, I'm hoping that the valgrind output from WoW on my native 32 bit
> box will be sufficient.
If you could produce an apitrace reproducing the leaks as reported by
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #14 from Chris Rankin ---
(In reply to comment #13)
> This may help you get a little further.
Actually, I'm hoping that the valgrind output from WoW on my native 32 bit box
will be sufficient. It does seem to show a suspiciously
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #13 from Nick Tenney ---
try:
$apitrace /usr/bin/wine /opt/wine/World\ of\ Warcraft/Wow.exe -opengl
-noautoload64bit
To record an apitrace of a little bit of play. It will generate a .trace file
that you can run through valgrind (I
https://bugs.freedesktop.org/show_bug.cgi?id=74539
Michel D?nzer changed:
What|Removed |Added
Attachment #95121|text/plain |application/octet-stream
mime
https://bugs.freedesktop.org/show_bug.cgi?id=74539
Michel D?nzer changed:
What|Removed |Added
Attachment #95119|text/plain |application/octet-stream
mime
https://bugs.freedesktop.org/show_bug.cgi?id=74539
Michel D?nzer changed:
What|Removed |Added
Attachment #95121|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=74539
Michel D?nzer changed:
What|Removed |Added
Attachment #95119|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #12 from Chris Rankin ---
Created attachment 95121
--> https://bugs.freedesktop.org/attachment.cgi?id=95121=edit
2nd valgrind output from 32 bit WoW
Again with the HD4670 AGP and the latest git:
commit
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #11 from Chris Rankin ---
Created attachment 95119
--> https://bugs.freedesktop.org/attachment.cgi?id=95119=edit
Valgrind output from 32 bit WoW
I have an extremely underpowered dual P4 box with a HD4670 AGP card that is
capable
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #10 from Chris Rankin ---
(In reply to comment #9)
> valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No
> such file or directory
More specifically: Valgrind is falling back to the x86_64 platform when
executing
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #9 from Chris Rankin ---
Has anyone ever "valground" a 32 bit executable on a box which is natively 64
bit, please? This bug is currently making it impossible to run Wow-64.exe:
http://bugs.winehq.org/show_bug.cgi?id=35582
That in
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #8 from Chris Rankin ---
(In reply to comment #7)
> You may need to recompile wine after installing valgrind, as mentioned in
> the wiki.
There is no "re"-compile of wine - it either works with Fedora's debuginfo
package or it
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #7 from Nick Tenney ---
I found this helpful for setting up wine and valgrind together:
http://wiki.winehq.org/Wine_and_Valgrind
You may need to recompile wine after installing valgrind, as mentioned in the
wiki. For a similar
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #6 from Chris Rankin ---
(In reply to comment #5)
> Please try getting more information about the leak(s) with valgrind
> --leak-check=full.
Do I need to do anything "special" to valgrind WoW.exe, seeing as it must be
invoked using
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #5 from Michel D?nzer ---
Please try getting more information about the leak(s) with valgrind
--leak-check=full.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #4 from Chris Rankin ---
I have finally managed to generate an "out-of-memory" condition while playing
WoW with git HEAD at:
commit f5bd5568abcc234c1c2b6a4bb67b880706f3caed
Author: Mark Mueller
Date: Tue Jan 21 22:37:20 2014
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #3 from Chris Rankin ---
(In reply to comment #2)
> I don't think this is it. These functions are called once per process.
Regardless, ed42e95404a51298ea878a0d1cdcbc473612706a is definitely "bad"
whereas
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #2 from Marek Ol??k ---
(In reply to comment #1)
> It looks like the first bad commit is this one:
>
> commit ed42e95404a51298ea878a0d1cdcbc473612706a
> Author: Marek Ol??k
> Date: Wed Jan 22 02:49:53 2014 +0100
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=74539
--- Comment #1 from Chris Rankin ---
It looks like the first bad commit is this one:
commit ed42e95404a51298ea878a0d1cdcbc473612706a
Author: Marek Ol??k
Date: Wed Jan 22 02:49:53 2014 +0100
r600g,radeonsi: consolidate remaining
42 matches
Mail list logo
