Texture
Texture copied to clipboard
[ASMultiplexImageNode] Avoid holding on to its lock while calling out to downloader
@nguyenhuy There's another case of the same pattern just below, in -didEnterVisibleState. Did you happen to see or by code inspection identify any risk of lock interleaving?
We should decide whether the node's lock or the downloader's lock is higher precedence, and then as long as we are using them in that sequence, it would not be necessary to unlock when calling the other.
I just happened to look at this method and noticed that we're doing it differently in ASNetworkImageNode.