Re: [Openexr-devel] Thread safety

[Larry Gritz]

Ah, I see, thanks for the explanation, Peter.

> (This does assume that IlmThread's Lock mechanism is compatible with the way 
> your threads are created).

I'm not sure I followed that statement. Huh?

My threads do each set up separate frame buffers.  It's too bad the framebuffer 
isn't an argument to readPixels/readTiles rather than set by a separate call to 
setFrameBuffer (which, duh, of course I should have spotted as the kind of 
non-atomicity that would be the fatal flaw).  I may be able to finagle a way to 
make a lock just around the setFramebuffer/readTiles pair.


> As always, the fastest way to read EXRs is to read as much of the file as 
> possible in a single call, and let the EXR library manage its own threads.

Ha ha, yeah, until you have 2 TB of image files you're accessing incoherently.


--
Larry Gritz
address@hidden