One trick is to give it a radioactive marker like they do in medical shows.
Have that instance you care about reference an instance of EmailMessage or some other class you aren't actually using. Finding the EmailMessage object should be easy because there is only one, and from there you can find the IronPython object you are after. I use RedGate instead of WinDbg, so I'm not sure this will work for you. If you try it, please let me know the results. Jonathan -----Original Message----- From: Lukas Cenovsky <cenov...@bakalari.cz> Sent: Monday, October 18, 2010 10:01 AM To: Discussion of IronPython <users@lists.ironpython.com> Subject: [IronPython] gcroot for ironpython object Hi all, I have an instance of IronPython object and I'd like to find out why it is kept in memory (I use weakref to check it is still in the memory). What is the best way to find the object in WinDbg so I can call gcroot for it? Or is there a better way to find out why my object is kept in memory? Thanks. -- -- Lukáš _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
