Problems in the hand are searching for a memory leak I've used the Develop: Refract, to show that my Which objects in the application are kept in memory when they should not be.
Three methods have been proposed to find the reckless link of these structures.
1 - Maybe there is a data structure that allows me to get a list of symbols in the context of my object, it would be ideal and direct.
2 - See the symbol table in the search for all defined namespaces and use the heap pile to determine where it is.
3 - Insert a hook from which a particular reference link has been changed or the following symbol is catching that link. I can use which symbols to reference my reference directly Are holding.
Is this possible? This type of introspection is the hard stuff, and I know Pearl very well, but I do not know how to do it. My research in Pandwalkar, which seems to be a key to him, is not born. Your thoughts
How about?
#! Use Perl Test :: LeakTrace; No_leaks_ok {# doubt code here}; It runs blocks many times, and then if all the Pearl values in the interpreter increases, test :: Lectres thinks that the memory leaks are.
No comments:
Post a Comment