See also: https://lists.webkit.org/pipermail/webkit-qt/2013-January/003410.html
Currently it is not possible to gracefully handle the case of a crashed/unresponsive QtWebProcess in WK2/QML. The idea is to add signals for that which would allow the QML developer to save any state that he might need, then trigger a reload and restore the old state or similar.
Created attachment 185771 [details]
The patch in principal looks okay to me, however, it will have to be rewritten a bit because QtWebPageLoadClient no longer exists in that form, but has been folded into QQuickWebViewPrivate a while ago.
Also, we might need to have a WebKit2 owner cc'ed for the sign off when the patch has been rewritten.
Created attachment 191471 [details]
Ping? Can we get this accepted please?
Comment on attachment 191471 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=191471&action=review
> + qWarning("WARNING: The web process has become unresponsive.");
I think that this isn't necessary, it can be noisy for applications using the signals directly.
> + qWarning("WARNING: The web process has become responsive.");
Even less value for this one :)
This looks good to me otherwise.
Created attachment 207864 [details]
Comment on attachment 207864 [details]
Clearing flags on attachment: 207864
Committed r153580: <http://trac.webkit.org/changeset/153580>
All reviewed patches have been landed. Closing bug.