#19413 [Ctl->Opn]: GD & freetype not thread safe

From: Date: Mon, 16 Sep 2002 20:27:06 +0000
Subject: #19413 [Ctl->Opn]: GD & freetype not thread safe
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-19491@lists.php.net to get a copy of this message
ID: 19413 Updated by: rasmus@php.net Reported By: brianh@kheldar.apana.org.au -Status: Critical +Status: Open Bug Type: GD related Operating System: OS/2 PHP Version: 4.2.3 New Comment: I really don't think an extension/library not being threadsafe is a critical issue for 4.3. There are dozens of extensions with thread safety problems and if we say that making every extension threadsafe is a requirement for 4.3 it will take us 12+ months before we can release it. Previous Comments: ------------------------------------------------------------------------ [2002-09-15 03:13:14] derick@php.net Setting this to critical so that it will be picked by somebody before 4.3 is released. Derick ------------------------------------------------------------------------ [2002-09-15 01:53:40] brianh@kheldar.apana.org.au This patch serializes access to gdImageStringFT & friends, curing the segfaults I'd been getting. http://silk.apana.org.au/pub/apache/gd_threadsafe_patch.txt ------------------------------------------------------------------------ [2002-09-15 01:34:18] brianh@kheldar.apana.org.au In testing Apache v2.0.40 running multi-threaded, I noticed regular exceptions occurring with concurrent requests for a GD generated image. I tracked it down to the fact that the way GD uses freetype is not thread safe (it uses a single static FT_Library object which the freetype docs specifically say shouldn't be shared between threads). ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19413&edit=1

« previous php.bugs (#19491) next »