Robert,

On Monday 27 August 2007 10:39:41 Robert Osfield wrote:
> Another user recently reported problems with loading text in a
> background thread, which fits your problem too.  This was recently and
> with the SVN version of the OSG so it looks like the problem persists.
>
> I suspect the problem is either in src/osgText/Font.cpp or the
> freetype plugin, or freetype itself.  If we can pinpoint where the
> problem it should be easy to fix - something like adding a mutex to
> serialize the freetype API access.
>
> I don't have an app that recreates this problem with rather limits my
> ability to reproduce and fix it.  So I either need an example that
> reproduces the problem or for others to dig into the relevant code and
> fix it.

I had a crashing problem related to osgText::Text.  The stack showed that the 
crash was happening in osgText::Text::setText.  This crash did not seem to 
happen when the freetype plugin was missing.  I was using the arial.ttf font, 
and I had the same problem on both Windows and Linux.

My code was creating a HUD compass tape along the bottom of the window.  The 
compass used the osgText::Text nodes to label the tape marks.  I was 
dynamically allocating the osgText::Text objects every time the view heading 
changed.

When I replaced the dynamic allocation with a preallocated pool of objects, 
the crash went away (i.e. I was not able to produce a crash ... it might 
still be dormant in threading issues).

To Summarize:
- The crash happened when using the freetype plugin
- The crash was triggered during calls to setText
- I did not change any of my setText calls
- Replacing the dynamic osgText::Text allocations fixed the crash

Thanks,
Justin
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to