Hi Melchoir, On Mon, Feb 9, 2009 at 10:38 PM, Melchior FRANZ <[email protected]> wrote: > Confirmed. However, in fgfs I got again a segfault with particles > and threading ... > > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb67d16f0 (LWP 32467)] > osgParticle::ParticleSystemUpdater::traverse (this=0x96be668, n...@0x9843150) > at /home/m/fgfs/osg/include/OpenThreads/ScopedLock:31 > 31 explicit ScopedLock(M& m):m_lock(m) {m_lock.lock();} > > Can't say more, as I had to throw the core file away (don't ask :-). > Now I'm helgrinding fgfs+osg, and after that I'll make another > fgfs run and will then explore the next core dump ...
I've just reviewed the ParticleSystemUpdater code and it looks correct. Accessing mutex shouldn't just cause a crash. The only time I could see it causing a crash is if the mutex itself is deleted and the pointer being used to access isn't dangling. The ParticleSystemUpdate has keeps ref_ptr<ParticleSystem> to the list of particle systems it's updating so dangling pointers shouldn't be an issue. Any chance that FlightFear is modifying the ParticleSystem/ParticleSystemUpdate within the cull traversal? What happens we you try differnt threading models like CullDrawThreadPerContext, SingleThreaded and DrawThreadPerContext? I'm turning in catch up with you in the morning. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
