This appears to happen for a similar reason as to why bug 10838 was causing memory leaks: a virtual method is being called from the Frame destructor, leading to the Frame version being called rather than the superclass as expected. As the Frame implementation is pure virtual, the runtime library aborts.
Created attachment 10882 [details]
Comment on attachment 10882 [details]
Landed in r16743.