On 4/14/13, Matt Madia <mattmadia@xxxxxxxxx> wrote: > Deleted referenceable object with non-zero ref count. After some further debugging with Matt, the problem is as follows: The check for a ref count of 1 + object on the stack fails to correctly detect that the object is in fact a stack object, because we're either unable to get thread_info, or the info object returned has stack_base and stack_end set to 0, which of course causes us to be unable to determine that the object is in the thread's stack range. Any ideas how to get around that? I suppose it's too early in the boot process to reliably get thread information? Regards, Rene