[Webkit-unassigned] [Bug 24551] [Qt] leaks in font-handling

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Mar 26 04:20:05 PDT 2009


------- Comment #8 from Kelemen.Balazs.3 at stud.u-szeged.hu  2009-03-26 04:20 PDT -------
I see. We can solve it locally like checking the pointer and if it is 0 then
creating a new FontPlatformData object. If it is a unique situation then it
would be enough. If it is just an example of how can bad happens then we must
find a more general solution. I guess it can be unique because the patch worked
form me (I could browse with QtLauncher without segfault after applied it).
I see two possibilities: 1. introduce a macro like USE_FONTCACHE and add
#ifdef-s when it is necessary
     2. implement a FontCache that provides the needed interface without

So, what do you prefer? Local solution, one of the two above, or something
Anyway, I think we must not return with a pointer of a newly created and
instantly released object from methods of FontCache.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list