I ran into this by accident when I triggered CORS on some data: images when it should not have been happening. Minimal leaking testcase: <img crossorigin src="data:a/a,"> What happens here is that we get to the nsCORSListenerProxy constructor in LoadImage, that errors out and we return. But we already have a cycle between the imgRequest and the imgCacheEntry at that point, so we lose. Patch coming up.
Created attachment 602255 [details] [diff] [review] Fix leaks on CORS failures in imagelib.
6 years ago