[osg-users] osgText: two thread-safety issues

[Glenn Waldron]

Robert,
I would like to make you aware of two thread-safety issues in osgText:

Font::getGlyph() is thread-safe, but it returns a shared Glyph object that
also needs protection. Glyph::getOrCreateTextureInfo, getTextureInfo, and
setTextureInfo can fail when creating Text objects from different threads.

Font::getCachedStateSets() returns a container that can be modified by the
Text::createStateSet() method. This container also needs mutex protection.

Glenn Waldron

[Robert Osfield]

Hi Glenn,

Thanks for the note. When I just back onto OSG maintenance work I'll
have a look into it. Should be in the next week or two.

Robert.

Post by Glenn Waldron
Robert,
Font::getGlyph() is thread-safe, but it returns a shared Glyph object that also needs protection. Glyph::getOrCreateTextureInfo, getTextureInfo, and setTextureInfo can fail when creating Text objects from different threads.
Font::getCachedStateSets() returns a container that can be modified by the Text::createStateSet() method. This container also needs mutex protection.
Glenn Waldron
_______________________________________________
osg-users mailing list
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org