On Wed, 2006-09-27 at 01:28 +0200, Alexander Sack wrote: > On Tue, Sep 26, 2006 at 04:18:38PM -0700, Keith Packard wrote: > > reassign 388739 thunderbird > > thanks > > > > On Tue, 2006-09-26 at 22:27 +0200, Alexander Sack wrote: > > > reassign 388739 fontconfig > > > thanks > > > > > > I reassign this to the fontconfig package as I think that the problem > > > might live there. Feel free to reassign back to me if you feel that > > > this issue is not related to a fontconfig bug. > > > > The issue is related to the new fontconfig package, but the bug is in > > thunderbird; it is destroying a resource which it shouldn't. This bug > > was masked by the old fontconfig behaviour which would never discard > > these resources. > > So would we get a resource leak if we do not destroy that > resource in thunderbird AND use an older version of fontconfig? > Otherwise, it would be hard to convince upstream to integrate such a > patch soon.
nope, the problem is thunderbird is freeing an object that they don't hold a reference to. I don't blame them, fontconfig reference semantics are completely broken... With old fontconfig versions, *nothing* in the cache could ever be freed, so you could destroy the same charset a million times and have no ill effect. Uncache objects, on the other hand, would eventually be freed and cause the program to crash. Newer mmap'd fontconfig versions just demonstrate this problem sooner. > #0 0xb79ffd17 in FcCharSetDestroy () from /usr/lib/libfontconfig.so.1 Calls to this function must match calls to FcCharSetCopy which increment the refernence count. -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
