Yup. It's a known bug that has been around since Firefox 0.3 or so, and can often lead into X process being huge (like 1-2 gigabytes etc) forcing you to restart X. It is caused by some technical solution that makes X to reserve some bitmap caches for Firefox, and the Firefox developers have refused to acknowledge the problem because fixing it would make Firefox look bad. It would mean that Firefox would actually show as what it is - the worst browser to what comes to memory requirements. In theory those bitmap caches should get always freed nicely, but especially when you put more stress on Firefox by for instance using larger amount of simultaneous tabs (200+) it starts leaking very hard and very fast.
-- /usr/bin/X leaks memory with firefox https://bugs.launchpad.net/bugs/111299 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
