Hi, I have done some further debugging and have gained a little insight, but have not yet solved the problem entirely.
What is happening goes as follows: After creation of my scene manager and the embedded ShadowStage object, my composite viewer (managing the viewports and the RenderAction) calls redraw which comes around in the ShadowStage::renderEnter method. This method then calls this->setData(pData, ..., ract), with a just created ShadowStageData object. Inside of this call a connection between the RenderAction and this StageData instance is established. Now on destruction of my composite viewer the render action is destroyed. This leads, by the established connection, to the destruction of the ShadowStageData instance. But, the setData(...) call also establish a change handler between the ShadowStage and the ShadowStageData instances. Now on destruction of my scene manager instance the embedded ShadowStage object is destroyed. This, however, yields to a change message to the already destroyed ShadowStageData instance. I think that this is not a destruction order problem since the my scene manager does have an idependent lifetime from the composite viewer. What is missing, IMHO, is a disconneting operation from the StageData destructor to the Stage instance. What do you think? Best, Johannes ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
