Comment 15 for bug 1401488

desrt just reminded me (after I reminded him :) that my apparent explanation of the bug doesn't make sense.

We're losing a reference to the GSource and the claimed unsafe callback should actually be safe already (as its caller is designed to hold a ref).

Although the workaround that's landed seems to perform well, I'm concerned as to understanding /why/ still...