Hi all,
I want to do
singleton->passiveWin[id]->render (singleton->action[id]);
in several threads on the same aspect.
In method RenderPartition::dropFunctor(DrawFunctor&, State*, Int32, bool)
which belongs to RenderAction, there is
"
DrawableStatsAttachment *st = DrawableStatsAttachment::get(actCore);
if(st == NULL)
{
DrawableStatsAttachment::addTo(actCore);
st = DrawableStatsAttachment::get(actCore);
}
"
which looks not deadlock-free to me (as it adds an attachment to the node),
"
DrawableStatsAttachmentTransitPtr DrawableStatsAttachment::addTo(
AttachmentContainer *obj)
{
DrawableStatsAttachmentTransitPtr st = DrawableStatsAttachment::create();
st->attachTo(obj);
return st;
}
"
Is there the possibility to move this out of the render traversal
into a preparation phase "add DrawableStatsAttachment"?
Or can StatsCollector be switched off completely?
How are resources handled during traversal on different windows?
Thanks a lot,
Christoph
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
