The actual channel calls ReleaseListeners in OnStopRequest, so there's no remaining link between it and the serialized load context in the parent actor.

This was worse than I expected. I feel dirty.

Comment on attachment 675395 [details] [diff] [review] Retain parent HTTP channel callbacks as long as the child might initiate operations that require them. Review of attachment 675395 [details] [diff] [review]: ----------------------------------------------------------------- ::: netwerk/protocol/http/HttpChannelParent.cpp @@ +387,5 @@ > +HttpChannelParent::RecvNotifyStartRequestComplete() > +{ > + if (mChannel) { > + bool pending; > + mChannel->IsPending(&pending); I am a bit worried about using IsPending. I'd rather have two state flags in HttpChannelParent telling you that you have received NotifyStartRequestComplete and OnStoprequest. When both are set -> do the cleanup. Nit: the cleanup code (3 lines) deserves its own method.

Comment on attachment 675395 [details] [diff] [review] Retain parent HTTP channel callbacks as long as the child might initiate operations that require them. I'm pretty sure this issue no longer matters once bug 805616 is fixed.

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258