All,
After further invesigation on why my thread is hanging, I narrowed it down to
when OSG creates an IntersectorGroup() object via the 'new' operator in the
intersection code.
Just for a sanity check, I did the following in the run() method of my thread:
char *start = (char *)malloc(4)
and
HI Shayne,
Doing a new really shouldn't cause any threading problems. Does you
app override new and delete? Is there something else unusual about
our set that might break new and delete's thread safety?
Robert.
On Thu, Nov 18, 2010 at 3:07 PM, Shayne Tueller
shayne.tuel...@hill.af.mil wrote:
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert
Osfield
Sent: Thursday, November 18, 2010 8:55 AM
To: osg-users@lists.openscenegraph.org
Subject: Re: [osg-users] thread hangs when LineSegmentIntersector is used...
HI Shayne,
Doing a new really shouldn't cause any threading problems
18, 2010 9:08 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] thread hangs when LineSegmentIntersector is used...
Robert,
Thanks for the reply. No, our app does not override new and delete. It's
using the standard operators in C++. I'm not sure on how to answer your last
question. Are you
All,
I have a two process application where one process loads the scenegraph for
rendering via CompositeViewer while the other process loads a subset of the
same scenegraph (terrain) for extracting database information. No rendering is
going on in the second process.
In the second process,
Hi Robert,
Thanks for the reply.
If LineSegmentIntersector does nothing to the scenegraph, I'm definitely not
modifying the scenegraph in the process that spawned the thread so there must
be something else going on that is causing the thread to stop running.
I have gone into the debugger and
6 matches
Mail list logo
