Julien Cristau <jcris...@debian.org> writes: > On Sat, Oct 18, 2014 at 15:34:59 +0100, Christophe Rhodes wrote: > >> This was reported to debian mailing lists here: >> <http://thread.gmane.org/gmane.linux.debian.devel.pulseaudio/4456> >> but I couldn't find a bug reported anywhere. At present, in an X session >> that >> is around a month old, the single persistent xprop process, whose parent is >> pulseaudio-start-x11, is consuming nearly 600MB of resident memory. >> > I replied to that report at the time, and I'm going to make the same > reply now. Somebody needs to send the patch to the xorg-devel list to > get it reviewed/applied upstream.
OK. Who is that "somebody"?
I have some kind of a working relationship with my distributor: I try to
contribute bug reports, to help out with upstream software that I'm
familiar with, and to record problems and potential problems that I
encounter with software that I'm less familiar with. I consider logging
this bug a (small) contribution to making Debian better, not least
because at the moment it looks like Debian might release with the
default desktop being effectively unusable after about a month's
operation on lowish-memory machines.
I have no working relationship with the upstream software developers. I
have no desire to subscribe to the xorg-devel list, to work out where it
actually is, to learn the community norms, to lobby for the patch or
other remedy; I don't even know whether it's by design that xprop leaks
memory ("#ifdef notused" suggests that it might be), and I do not
consider myself competent to argue either way. What happens if
xorg-devel says "oh, right, let's disable the -spy option"? I simply do
not have time to open that can of worms for myself.
So, I wonder, where can I find a team of people who are interested in
the quality of the x11 software as shipped in Debian? Who (probably) do
already have some kind of working relationship with the upstream
software developers? Who (probably) know where the relevant mailing
lists live, how to engage with the developers, how to negotiate the
optimal outcome? Where could such a team be found? Well, maybe there
isn't one, in which case I will work around the problem; but if
submitting a bug in software that Debian distributes and executes by
default isn't one step on the road to improving the situation, I'm
sorry.
In case it's not clear through the sarcasm: if your response indicates
that no-one in the debian-x maintainers is going to take this forward, I
will be sorry, but I will not be doing it myself either. Now, please
excuse me; I must go and do the washing up.
Christophe
pgpuIZFHvnWYQ.pgp
Description: PGP signature
