Comment 1 for bug 887255

Epsy's recent change made a stacked object get added to a hidden linked list where it is destroyed from. I suspect that's causing the threading trouble you observe, the callstack is from shortly after the destruction and the object (the gServerInfoFavorite) is actively getting used; the nAddress part of it contains thread sync code.

I didn't even get that far in local testing, the debugging memory manager complained earlier; so please verify whether the issue is solved.