[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

GitLab Migration User  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #8 from GitLab Migration User  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/499.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #7 from Marek Ol??k  ---
Leaking a radeon_winsys allocation is hardly an issue. There is only one
instance of the winsys per process anyway. This is really harmless. I wouldn't
even bother trying to fix this leak (if there really is a leak).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #6 from Chris Rankin  ---
(In reply to comment #5)
> valgrind finds one 352 byte leak with celestia. That can't possibly explain
> the issues you're having with WoW.

I raised this as a separate issue for a reason... ;-). But I doubt that Mesa
contains functionality that is *specific* to WoW; other apps *must* be affected
by #74549 - although perhaps not as noticeably.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #5 from Michel D?nzer  ---
(In reply to comment #4)
> [...] since valgrinding 32 bit WoW on a 64 bit box is currently beyond me,

As suggested in your WoW bug report, please try valgrind on replaying an
apitrace instead.


> I am hunting for memory errors in other workloads instead, in the hope that
> they might provide some insight.)

valgrind finds one 352 byte leak with celestia. That can't possibly explain the
issues you're having with WoW.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #4 from Chris Rankin  ---
(In reply to comment #2)
> Please describe the problem in more detail. Why do you think there is a leak?

(There's also an underlying hypothesis that WoW cannot possibly be the only
program in existence to be experiencing memory problems under Mesa. However,
since valgrinding 32 bit WoW on a 64 bit box is currently beyond me, I am
hunting for memory errors in other workloads instead, in the hope that they
might provide some insight.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #3 from Chris Rankin  ---
(In reply to comment #2)
> Please describe the problem in more detail. Why do you think there is a leak?

I think there's a leak because "Valgrind says there's a leak" and "Valgrind is
a program that finds memory leaks". Simple, really.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #2 from Michel D?nzer  ---
(In reply to comment #1)
> Having recompiled the current Mesa from git, it looks as if
> radeon_winsys_destroy() in src/gallium/winsys/radeon/drm/radeon_drm_winsys.c
> is not being called on exit.

That only explains 352 leaked bytes though, over the whole lifetime of the
celestia process.


Please describe the problem in more detail. Why do you think there is a leak?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

--- Comment #1 from Chris Rankin  ---
Having recompiled the current Mesa from git, it looks as if
radeon_winsys_destroy() in src/gallium/winsys/radeon/drm/radeon_drm_winsys.c is
not being called on exit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 75732] [r600g] Memory leak with celestia, RV790

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75732

Chris Rankin  changed:

   What|Removed |Added

Summary|Memory leak with celestia   |[r600g] Memory leak with
   ||celestia, RV790

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: