Hello Rene,
Rene Weller wrote:
>> Have you looked at a stack trace of the crash, does it involve the
>> shadow code?
>
> The stack trace seems not to be very usefull because the crash happens not
> directly in the shadows code.
hm, I got lucky, for me it crashed somewhere inside
ShadowViewport::changed().
>> Do you only see the crash if you add the shadow stuff, or more precisely
>> what makes you think the shadows are the cause?
>
> Before including the shadows, everything works fine :-). However, I attached
> a minimum example based on the multithreading tutorial. If you undefine the
> SHADOWS in line 27, you can see that everything runs, but with the shadows
> enabled, I get a crash when
> osg::Thread::getCurrent()->getChangeList()->applyTo(1); in line 163 is called.
ok, the problem is that the ShadowVP has many member variables that are
not held in fields and therefore are not synced between the two aspects
the threads run in. On top of that many of these objects were only
created/destroyed in the onCreate/onDestroy virtual functions that only
runs once per object (not for each aspect copy), so they only existed in
the anim thread's aspect.
I fixed that and it does not crash any more. Can you give it another try?
Cheers,
Carsten
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
