On Wed, Feb 25, 2009 at 4:23 AM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, 25 Feb 2009 03:15:35 +0100 Markus Rechberger <mrechberger@xxxxxxxxx> wrote: > >> On Wed, Feb 25, 2009 at 3:02 AM, Mauro Carvalho Chehab >> <mchehab@xxxxxxxxxxxxx> wrote: >> > On Tue, 24 Feb 2009 13:57:20 -0800 >> > Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >> > >> >>> > In the output of /proc/slab_allocators the number of blocks allocated by >> >> > usb_alloc_urb() increases, however, the xawtv is no longer running: >> >> > >> >> > size-2048: 18 usb_alloc_dev+0x1d/0x212 [usbcore] >> >> > size-2048: 2280 usb_alloc_urb+0xc/0x2b [usbcore] >> >> > size-1024: 100 usb_alloc_urb+0xc/0x2b [usbcore] >> >> > size-128: 10 usb_alloc_urb+0xc/0x2b [usbcore] >> >> > >> >> > Each time xawtv is started and stopped the value increases at the >> >> > usb_alloc_urb(). >> >> > >> >> > Expected result: the same memory usage is reached again after xawtv exited. >> >> > >> >> >> >> I assume this is a v4l bug and not a USB core bug? >> > >> > I guess this is a v4l bug. We've found several memory leaks on em28xx driver, >> > fixed at the development -git: >> > >> > http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git >> > >> > I'll do some tests again with the latest em28xx driver to double check if it is >> > there any other memory leak. If not, then we could replicate the same approach >> > into uvcvideo. >> > >> >> haha you never even had a look at the issue itself. > > What a perfectly useless comment. > not more or less useless than the one before http://mcentral.de/pipermail/em28xx/2009-February/002446.html I followed the other em28xx work too and there has not been anything which addressed that issue. Markus -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
