Others include: * MainResourceLoader's error handling into DocumentLoader::mainReceivedError() * MainResourceLoader::cancel into DocumentLoader::cancelMainResourceLoad * m_identifierForLoadWithoutResourceLoader handling, plus remaining synthesized ResourceLoadNotifier callbacks.
Created attachment 193878 [details] patch
Created attachment 193885 [details] Fix compile error
Comment on attachment 193885 [details] Fix compile error r=me
Comment on attachment 193885 [details] Fix compile error Clearing flags on attachment: 193885 Committed r146239: <http://trac.webkit.org/changeset/146239>
All reviewed patches have been landed. Closing bug.
Mac build fix landed in http://trac.webkit.org/changeset/146242.
(In reply to comment #4) > (From update of attachment 193885 [details]) > Clearing flags on attachment: 193885 > > Committed r146239: <http://trac.webkit.org/changeset/146239> It made 60 tests crash on Qt: http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Debug/builds/28194 cc-ing Qt folks for investigation
This also caused bug 112811.
(In reply to comment #7) > (In reply to comment #4) > > (From update of attachment 193885 [details] [details]) > > Clearing flags on attachment: 193885 > > > > Committed r146239: <http://trac.webkit.org/changeset/146239> > > It made 60 tests crash on Qt: http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Debug/builds/28194 > > cc-ing Qt folks for investigation Are these tests still crashing? I'd be happy to help diagnose if you have a stack trace.
(In reply to comment #9) > > It made 60 tests crash on Qt: http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Debug/builds/28194 > > > > cc-ing Qt folks for investigation > > Are these tests still crashing? I'd be happy to help diagnose if you have a stack trace. No, the crashes went away somewhere between r146261-r146283.
(In reply to comment #10) > (In reply to comment #9) > > > It made 60 tests crash on Qt: http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Debug/builds/28194 > > > > > > cc-ing Qt folks for investigation > > > > Are these tests still crashing? I'd be happy to help diagnose if you have a stack trace. > > No, the crashes went away somewhere between r146261-r146283. Ah, yeah, I fixed a bunch of chromium asserts in http://trac.webkit.org/changeset/146267, which probably had the same root issue. Thanks!