| Summary: | gtk+2.12.1-r1 kills mozilla thunderbird | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | nm (RETIRED) <nightmorph> |
| Component: | New packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | gnome |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| URL: | https://bugzilla.mozilla.org/show_bug.cgi?id=389801 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 196481 | ||
| Bug Blocks: | |||
|
Description
nm (RETIRED)
2007-11-15 21:43:23 UTC
Not a gtk+ problem. We will not go back to using malloc for GtkBorder and GtkRequisition structures by reverting gtk+ upstream relatively huge improvements to memory handling (as huge as using the perfect fit memory allocator for a certain type of structure can be) of these widely copied around structures. This is a gecko problem that is fixed in 1.8.0.14 and 1.8.1.8 as per https://bugzilla.mozilla.org/show_bug.cgi?id=389801 Feel free to convert this to a bug for the mozilla team to make sure the stable versions contain a fix. We discussed this issue a month or more back with armin76 over IRC and it maybe didn't get a bug and therefore wasn't a blocker for the gtk2.12 compatibility tracker bug. Reopening it to give it to the mozilla guys mozilla-thunderbird problem in using buggy gecko that uses wrong deallocation function for GtkBorder and GtkRequisition then. Bug 175803 might be caused by this as well, but the backtrace looks quite different so not sure (also not sure why 175803 didn't get passed on to anyone if it's supposedly a theme problem, which is unlikely..). The obvious fix is to stop slacking and bumping TB from current latest in portage 2.0.0.6 version to last upstream 2.0.0.9 version or anything released after it was fixed in gecko (that has the necessary version cited above). This is probably urgent, as a broken TB is no fun for a release. The upstream bug is here: https://bugzilla.mozilla.org/show_bug.cgi?id=389801 It has been fixed upstream since end of September, so probably even 2.0.0.7 or 2.0.0.8 has it fixed if two day old 2.0.0.9 is too fancy for fasttracking to stable. 2.0.0.9 is meant to go stable, so hopefully that'll resolve this. (In reply to comment #4) > 2.0.0.9 is meant to go stable, so hopefully that'll resolve this. Re-upgraded to gtk+-2.12.1-r1 and upgraded to the newly stabilized tb-2.0.0.9, and tb works just fine now. Thanks. amd64 has 2.0.0.9 stable, nothing left for us here -> removing CC Closing, then |