Summary: | mail-client/mozilla-thunderbird-2.0.0.22 triggers X memory leak with >=dev-libs/nspr-4.8 >=dev-libs/nss-.3.12.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Kahle (RETIRED) <tomka> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | facorread |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Kahle (RETIRED)
![]() Hello, so we have a problem specific to one of those libraries. So I'd like to suggest a preliminary test for anybody interested: emerge Thunderbird with the stable version of one of the libraries, and the unstable version of the other; check whether the memory leak persists. Then do the opposite thing and check again. I do not quite understand what do you mean by "preserve the old ones[versions of the libraries]." Is it some slot? There are no slots for these libraries. I do not have the old versions, but I do not have time to run this test. I will keep a Thunderbird instance running in my memory to check for the leak. Fabio: preserve libraries is a new portage feature (in masked versions of portage, as Thomas mentioned) that allows shared library files from an old package version to temporarily stay on the system after an upgrade; then they will be removed when all the applications have been rebuilt against the new library version. It makes upgrading more convenient, without making the library be slotted and installable fully in parallel (only the required .so files are kept from the old version, and not other files like header files that might collide with the new version). So, that's how come Thomas could have thunderbird still using old libraries even though these library packages are not slotted. BTW, good suggestion to try different combinations of the old and new libraries, it will be nice if someone volunteers to do this... I cannot reproduce this bug anymore. I am closing it as invalid since I now believe that I have triggered the high memory usage by some other factor, which I did not properly control for. |