On 04/04/2015 06:21 PM, Holger Hans Peter Freyther wrote: > On Fri, Apr 03, 2015 at 11:36:55PM +0200, Roland Plüss wrote: > >> The application holds C++ resources by reference counting outside >> Smalltalk. The resources have to be cleaned up before the Smalltalk >> module is shut down. This is because the engine keeps running valid with >> the scripting module shut down (so you can start/stop it multiple >> times). Without proper finalization the reference counts are off leading >> to random crashes somewhere down the line. > In regard to leaks "allOwners" can be of help. The tooling is a > bit difficult but it can be interesting to see it. > > Finalization/Shutdown. You should terminate all processes to some > degree and wait for the "finalization listener" to have executed > and shutdown everything. What you mean with shuting down all processes? As far as I know GST knows only one process: the main process. When I'm outside the main process should it not be the case that each call to gst_perform or similar is conclusive, hence finishing up? So how would a finalization listener work once you exit again the byte code? Similar how would saving a snapshot work? There you have to also save the image and somehow "exit" back into C++ land to shut down. Am I missing here something?
-- Mit freundlichen Grüssen Plüss Roland Leader und Head Programmer - Game: Epsylon ( http://www.indiedb.com/games/epsylon ) - Game Engine: Drag[en]gine ( http://www.indiedb.com/engines/dragengine , http://dragengine.rptd.ch/wiki ) - Normal Map Generator: DENormGen ( http://epsylon.rptd.ch/denormgen.php ) - Sowie verschiedene Blender Export-Skripts und Game-Tools
signature.asc
Description: OpenPGP digital signature
_______________________________________________ help-smalltalk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-smalltalk
