Summary: | gnome-base/nautilus-2.22 uses huge amount of RAM while browsing some directory with videos inside | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Melentyev <andrey.melentyev> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrey Melentyev
2008-04-05 17:14:27 UTC
I just browsed through half a gigabyte worth of pictures and through 3 seasons worth of AVI files (that nautilus had never thumbnailed before) and basically, I can't reproduce. Indeed, totem-video-thumbnailer can grow quite big but the core nautilus process barely grew in virtual size from 99M to 101M (and that's virtual memory, so it's probably just the mmap'ed thumbnails). Resident memory and shared memory barely moved either. Thumbnails are not generated by nautilus directly, the fd.o/xdg standard more or less mandates an external application, which is how nautilus handles them. So even if the totem-video-thumbnailer leaks memory like a 2 year old drools, the thumbnailer is really short lived process, so it really doesn't matter. My advice, if you really want to debug this, you'll have to start with a clean user with an empty gconf and use memcheck and massif (both part of dev-util/valgrind) to figure out where the memory is going. Ping upstream about this, maybe they'll be able to help you out. Thanks I'm not talking about virtual size, and the size is bigger than 100Mb. Anyway, it seems that some Ubuntu users have some similar troubles with nautilus-2.22, so I believe it will be fixed in future releases of GNOME. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/187547 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/204413 (In reply to comment #2) > I'm not talking about virtual size, and the size is bigger than 100Mb. I was just pointing out that in my case, none of the memory sizes reported by "top" grew. And if any of the lower level memory stats had grown, virtual memory would have grown too. But I digress :) > Anyway, it seems that some Ubuntu users have some similar troubles with > nautilus-2.22, so I believe it will be fixed in future releases of GNOME. Seems that Ubuntu devs are having a hard time reproducing the issue too. If you can reproduce the issue easily, then I suggest you follow the Ubuntu Valgrind procedure with a few differences. 1) add "splitdebug" to FEATURES in make.conf 2) use "-O2 -g" in your CFLAGS 3) rebuild nautilus and glib That should give you a proper backtrace and symbols in valgrind. If you can, please open a bug in Gnome's bugzilla, referencing this bug and the Ubuntu ones. That should help everyone to fix the issue. And for the record, don't expect Ubuntu to fix all Gnome bugs. They've closed their share of bugs because they couldn't reproduce ;) Thanks |