Remove bogus assert from ImageLoader
Created attachment 178298 [details]
From reading the ways m_failedLoadURL is used, it seems like it's safe to just remove this assert, but I'm not at all an ImageLoader expert so I'm looking for help from the reviewer to decide if I need to do something other than remove the assert.
Comment on attachment 178298 [details]
I think that the gist of this assertion is to say that the function doesn’t do what anything appropriate with the failed load URL, which the original programmer thought was OK because that can never happen. Removing the assertion is clearly OK, but I think that additional work, such as clearing m_failedLoadURL, may be needed.
Clearing m_failedLoadURL seems reasonable in this case, and at worst will just cause a re-fetch, it looks like. Shall I just do that?
Created attachment 179514 [details]
Darin, can you take another look at this?
Comment on attachment 179514 [details]
Clearing flags on attachment: 179514
Committed r138724: <http://trac.webkit.org/changeset/138724>
All reviewed patches have been landed. Closing bug.
It appears that this patch broke WebKit1.MemoryCachePruneWithinResourceLoadDelegate:
On the other hand,
says it’s r138726, which is quite inconceivable.
Filed https://bugs.webkit.org/show_bug.cgi?id=106051 to track the failure.