Hi Matt, I'm not too familiar with the jasper plugin, as I'm not the author or user of it, so I'm afraid I won't be able to comment much directly. General things it would be worth looking at to double check jasper thread safety - there is chance it's not thread safe, or that there is restrictions to this.
Other plugins in the OSG are either thread safe already, or use a mutex to serialize access to functional parts of the plugins. Serialization of all access is rather a crude solution though as it'll throw away the multi-threaded nature of reading, but in some cases it's the only thing you can do if the 3rd party code isn't thread safe. Robert. On Wed, Feb 2, 2011 at 5:07 PM, Matt Schafer <[email protected]> wrote: > We're using the OSG Jasper based plugin 2.8.3. The program dies in the > readImage function with the filename string argument. It references a null > pointer returned from the jasper jas_image_decode function that can be > returned if it found an error. It looks like there is some global data in > jasper setup during the jas_init that the decode routine uses. The jas_init > and jas_image_clearfmts is called each time a file is read and in some other > spots in the the ReaderWriterJP2 file so I'm guessing concurrent call's can > mess up the config data from the other. We're trying out a fix that will > just do the init once in the ReaderWriter constructor and return an error on > the null pointer. > Thanks, > Matt > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=36287#36287 > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
