Comment # 6
on bug 60028
from Dave Witbrodt
I do not know how to interpret these findings. I am not a developer, and work
with the few tools that I (sort of) know how to use much more slowly than
experienced developers would. I ran out of time over the weekend, and will
have
to investigate further this coming weekend.
I have been trying to think of possible explanations:
- could a later commit causes a similar (or identical)
memory leak to the one caused by 4ac0533a?
- is the problem really located somewhere else
besides in the kernel DRM, such as in Mesa, with
it being triggered by more than one kind of
code change in the DRM?
I thought that the bisection would be conclusive, but the failure of the revert
attempts undermined my goal. If no one demands that I bisect using one of the
drm-airlied branches, then I will try another custom branch which drops the
commit first causing the leak, and see if any later commits also cause a leak.
(If a developer demands that I bisect an upstream branch, I'll do that
instead.)
Is there anything else I can do to be helpful at this point?
Can any of you confirm/reproduce this memory leak on your own systems?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
