| Summary: | www-client/firefox, mail-client/thunderbird ebuilds should check RAM+swap size | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sasha Polonsky <apl> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | minor | CC: | cruzki123, denkpadje, herrtimson, jdhore, tsmksubc |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Screenshots showing memory usage | ||
|
Description
Sasha Polonsky
2012-06-04 22:39:33 UTC
Firefox and Thunderbird both have a check to ensure that 4G is avaliable, it warns if failure is possible. I am not gonna make them errors as any combination of useflags can change this effect. The "4GiB" check is just for disk space at ${PORTAGE_TMPDIR}. Maybe 512MiB memory+swap are not enough, at least not for all three of them at the same time.
Giving this one to mozilla. Please file a separate bug for chromium. Perhaps on that little an amount of ram you should use firefox-bin or thunderbird-bin or google-chrome (the precompiled binary packages of firefox, thunderbird and chromium, respectively). Created attachment 314403 [details]
Screenshots showing memory usage
to Kai Damm: I have attached a screenshot from my Gnome desktop. It shows firefox with four tabs, thunderbird and memory usage shown by top in the terminal window. As you see, only 478 out of 512M of RAM are used and swap is not used at all.
Okay, I'm not affected by the bug, I have plenty of RAM and disk space. I just wanted to comment that the 4G mentioned in comment #1 are not the cause of the bug report. Checking the sum of the space requirements of all to-be-merged packages would be a nice portage feature, but that's clearly not in the scope of this bug. Just to clarify: With comment #2 I meant the memory required to emerge the packages, not the memory needed while running the programs. According to your experience, the threshold should be raised. There definitely is a warning. Even with enough RAM/space, there is at least the message "Checking for at least 4GB... and 512MB..." in emerge's output. To let emerge fail in that case would be excessive, because the actual requirement cannot be predicted - I have seen firefox emerge successfully on a system with 3.2 GiB space left, despite the warning about 4GiB. The same applies to the RAM requirement - with different use flags this might be very different. *** Bug 420155 has been marked as a duplicate of this bug. *** The same was reported back in february: https://bugs.gentoo.org/show_bug.cgi?id=402359 Since then, I experienced this issue with all firefox-12.0-revision + 13.0: 4GB RAM + 4GB SWAP, system stays unusable for minutes while linking. Comment on attachment 314403 [details]
Screenshots showing memory usage
Please remember to change mimetype to match appropriately.
I have this issue with a 2GB RAM + 1GB SWAP. Moreover, I even have had problems with a 4GB RAM machine so I think that the pre merge check of 4 GB of RAM + SWAP is needed as well as the 8GB of disk space. Firefox needs approx. 2gb of ram during linking - without debug flags on amd64 with -j4 ram consumption goes up to 3gb for the compiling and doubles up to 6gb with debug flags. So yeah, if it is not much of a deal to implement a check for this, I'd appreciate it. If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team |
