J
jankeir
Guest
Currently we can use DynObjects to log where objects are created and deleted, but if they are not deleted by the garbage collector it can sometimes be hard to find where a reference is kept to an object. For PASOE we can see the objects, but not the references at: http:// /oemanager/applications/ /agents/ /sessions/ /stacks That would be a good place to visualize the references. For non PASOE, programmatic access to reference, ie through an object property would be an option. An extra logentry that logs each increase and decrease of the reference counter + the location would also be usefull for hard to reproduce issues, where it is difficult to inspect the objects at runtime, however this is probably not sufficient because the amount of logging that would create would be so massive that it would only be desirable to use it if all other options to find the problem fail.
Continue reading...
Continue reading...