OpenSceneGraph Forum Forum Index OpenSceneGraph Forum
Official forum which mirrors the existent OSG mailing lists. Messages posted here are forwarded to the mailing list and vice versa.
 
   FAQFAQ    SearchSearch    MemberlistMemberlist    RulesRules    UsergroupsUsergroups    RegisterRegister 
 Mail2Forum SettingsMail2Forum Settings  ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
   AlbumAlbum  OpenSceneGraph IRC ChatOpenSceneGraph IRC Chat   SmartFeedSmartFeed 

osgText: two thread-safety issues


 
Post new topic   Reply to topic    OpenSceneGraph Forum Forum Index -> General
View previous topic :: View next topic  
Author Message
gwaldron (Glenn Waldron)
Appreciator


Joined: 25 Aug 2011
Posts: 242

PostPosted: Tue Jul 31, 2018 2:54 pm    Post subject:
osgText: two thread-safety issues
Reply with quote

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

------------------
Post generated by Mail2Forum
Back to top
View user's profile Send private message
robertosfield
OSG Project Lead


Joined: 18 Mar 2009
Posts: 12324

PostPosted: Tue Jul 31, 2018 3:56 pm    Post subject:
osgText: two thread-safety issues
Reply with quote

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.
On Tue, 31 Jul 2018 at 15:54, Glenn Waldron <> wrote:
Quote:

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



------------------
Post generated by Mail2Forum
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    OpenSceneGraph Forum Forum Index -> General All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Similar Topics
Topic Author Forum Replies Posted
No new posts How can we make 'osg' thread and 'ui'... mirro General 1 Mon Jul 01, 2019 2:36 am View latest post
No new posts Huge perfomance issues axilmar General 9 Thu May 30, 2019 10:53 am View latest post
No new posts Colored Bounding Box over osgText::Text dhhabyc General 1 Fri Apr 05, 2019 12:43 pm View latest post
No new posts CPU Performance issues with AMD 2700 ... robertosfield General 10 Mon Apr 01, 2019 2:01 pm View latest post
No new posts osgText::Text dissapears when reparen... dhhabyc General 1 Wed Mar 27, 2019 1:48 pm View latest post


Board Security Anti Bot Question MOD - phpBB MOD against Spam Bots
Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP