Comment # 16 on bug 998850 from Peter S�tterlin

(In reply to Vlastimil Babka from comment #14)
> (In reply to Peter S�tterlin from comment #12)
> > In any case it is not a Tumbleweed-bug, so I guess it can be closed.
> 
> I wouldn't be so sure about it. If the plugin (which is not a tumbleweed
> package then, IIUC?) was leaking its own memory, then sure. But if it's
> causing a memory leak in *kernel* memory, it's suspicious and probably a
> kernel (video driver?) bug.

Indeed, the plugin is not a Tumbleweed package, but compiled from source
myself, and the package is basically unmaintained since 2003.....

It is however not doing any memory allocation by itself (at least greping for
alloc does not give any result).

> Does the slab memory get freed when you kill/restart X?

No, it stays occupied, even when switching the system to emergency mode.

> > Sorry for the wrong alarm (but at least I have learned quite something about
> > kernel tracing, which is highly appreciated!)
> 
> A trace with full stack (see my previous comment) could still be useful.

Lets see if I can make some sense of it:
echo bytes_alloc==4096 >
/sys/kernel/debug/tracing/events/kmem/kmem_cache_alloc/filter
echo 1 > /sys/kernel/debug/tracing/options/stacktrace 
echo 1 > /sys/kernel/debug/tracing/events/kmem/kmem_cache_alloc/enable
cat /sys/kernel/debug/tracing/trace > stacktrace
If this is correct, the output is in the next attachment.