Hi Gert, I did fix some threading issues in osgText in the SVN version of the OSG. You could try patching your local OSG version with these changes. Unfortunately I can't recally off the top of my head what changes would be required, lots have been made since 1.2. SVN will have all the changes though, but they for the threading fixes the changes do propagate into the core osg, osgUtil libraries so you might need to patch more than 1.2.
Robert. On 4/12/07, Gert van Maren <[EMAIL PROTECTED]> wrote:
Hi guys, We're getting crashes in osgText when running on dual core or hyperthreading machines. (crashes are gone when disabling dual core in the bios) First error (not fatal) for every character in osgtextd.dll: Font::Glyph* glyph = activefont->getGlyph(charcode); Error: Run-Time Check Failure #0 - The value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention 2nd fatal error: in osgd.dll Unhandled exception at 0x00611db2 (osgd.dll) in v3_viewerd.exe: 0xC0000005: Access violation reading location 0xfeeefeee. Looks like a memory error. We do only modify the scene graph during the update phase ie. between viewer.sync() and viewer.frame(); We use OSG1.2. I understand 1.3/2.0 is more thread safe but still would be nice to get 1.2 stable on dual core (windows) machines. Anybody else have this problem -> suggestions? Thanks Gert -- Gert van Maren Head of Research & Development K2Vi Virtual Reality Software Data Interface Technologies Ltd Phone: +64 21 2855581 Email: [EMAIL PROTECTED] Web: http://www.k2vi.com _______________________________________________ osg-users mailing list [EMAIL PROTECTED] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [EMAIL PROTECTED] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
