Hi Johan,
Johan Robben wrote:
>> I've also written an activeX component and I've given up
>> on trying to call osgExit. :-) The clean-up in OpenSG
>> does not always work.... Just exit and all resources should
>> be freed. Not very clean, but it works.... Are you using
>> a debug build? Same behaviour in Release?
>
> Yes, I have the same behaviour in Release.
> It seems a resource does not free a lock.
> Is there any way to find out which resource it is ?
If you're using a PassiveWindow the only resources that I could think of are
the
locks. There is not a lot of locks in OpenSG, and they are all using the
OSG::Lock abstraction class. If you could could some debug output/breakpoint in
WinThreadLockBase::aquire, that might give us a hint on where it hangs. I have
no clue how to debug an ActiveX control, so I don't know if that's feasible.
Hope it helps
Dirk
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
