| Summary: | www-client/mozilla-firefox-2.0.0.2: memory leak resulting in OOM | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | William Pitcock <nenolod> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | CC: | dblaber, kashmonkey15, sgtphou |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.mozilla.org/show_bug.cgi?id=259672 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
William Pitcock
2007-03-28 23:36:22 UTC
Oh, I just realized that the emerge --info for my G4 PowerMac 3,5 got screwed up. The profile/CFLAGS for that should be considered for ppc32/G4 respectively. At any rate, that is not relevant to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=259672 is another bug that should be considered blocking forced adoption of 2.0 into stable, as it can cause an OOM in the X server. Additionally, this seems to be related to the new ThreadManager code, of which many bugs are reported at Mozilla. (sorry for the bugspam.) kash 27942 1.4 7.3 334324 70876 ? Sl 20:24 2:51 /usr/lib/mozilla-firefox/firefox-bin Reproduced locally. As you've noted, this is not a Gentoo-specific issue -> UPSTREAM. (Also not that heavy memory usage != memory leak) No. It is a gentoo bug because according to GWN, Firefox 1.5 is being deprecated for Firefox 2, which has this bug. Firefox 1.5 does not cause my systems to fail with an active OOM killer (full RAM+swap) after a few days of heavy use. As such, reopening. Additionally, the bug IS a memory leak. If it was high memory usage, then launching it and using it for a short amount of time would cause an OOM as the memory would have been mapped already. Assigning bug to correct herd. Well, you'll have to migrate to 2.0 anyways. Starting 26 April, 1.5 will be unsupported by Mozilla, so... How 'bout we keep 2.0 unstable and let 1.5 be the stable, until Mozilla fixes their mistakes? (In reply to comment #10) > How 'bout we keep 2.0 unstable and let 1.5 be the stable, until Mozilla fixes > their mistakes? > Still unsupported by Mozilla after 26 April...if they don't support it, we don't either. If you're unhappy with that, blame them, not us. And you can keep the ebuilds in your local overlay. (In reply to comment #9) > Well, you'll have to migrate to 2.0 anyways. Starting 26 April, 1.5 will be > unsupported by Mozilla, so... > While that's great and all, I'm sure that Debian's security team will be stepping in for sarge -- in which case, there will be security fixes. Fact is, 1.5 does not cause OOMs. Until 2.0 does not, it is not a suitable replacement for Firefox 1.5. I don't like to add to a noisy bug by asking that it not be a forum. but.. can we please stop treating this bug like a forum? thanks. (In reply to comment #12) > > While that's great and all, I'm sure that Debian's security team will be > stepping in for sarge -- in which case, there will be security fixes. > > Fact is, 1.5 does not cause OOMs. Until 2.0 does not, it is not a suitable > replacement for Firefox 1.5. > Debian doesn't use Mozilla Firefox. It's like you're asking to me to keep www-client/mozilla, which had a lot of security vulnerabilities. We're not going to have some vulnerable and unsupported app. If you're unhappy with that, i've already said, keep the ebuilds in your local overlay an blame Mozilla for dropping support of 1.5 series. There's going to be a lot of problems if 2.0 stays stable. It's unstable, and should be treated by the portage team as such. What does the portage team have to do here? The portage team only takes care of sys-apps/portage, not the entire tree. All the Mozilla products in the tree belong to the mozilla herd/team, and i'm from that herd. And i'm telling you, www-client/mozilla was not dropped when Mozilla dropped support of it because a lot of packages depended in it. No package depends on www-client/mozilla-firefox-1.5*. There's no way we are going to support _ANY_ package which is unsupported upstream. Again, we're not dropping 1.5 because we want, we are doing so because it's unsupported upstream and when some new exploit gets discovered it won't be fixed. Make Mozilla to support it after that date and we'll keep it. Else it will get removed. Feel free to create a public overlay with those ebuilds. And again, it's being dropped by Mozilla, not us. As others have explained, this bug is _nothing_ to do with us, and everything to do with upstream. The memory leak you mention doesn't just affect Mozilla Firefox on Gentoo Linux, or even Linux in general. I've seen similar memory leaks on the Win32 port of Firefox too. I'd suggest looking at the bug linked above. |
