|
From: Braden M. <br...@en...> - 2010-04-01 19:57:27
|
On 3/29/10 4:58 PM, Braden McDaniel wrote: > I'm still trying to get a handle on exactly what's going on > here. I'm getting closer; I think I'm looking at a race between some > stream handling threads. But I haven't isolated it yet. This may or may not be the case. Regardless, there is definitely something screwy going on in the PNG decoder. I think what's happening is that for some images, the decoder is not detecting the number of pixel components correctly and consequently isn't giving libpng a big enough buffer to work with. libpng calls then proceed to stomp all over memory (which on my machine appears consistently to be the browser's node_metatype_registry); hilarity ensues. -- Braden McDaniel <br...@en...> |