-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Fix crash when calling QObject::disconnect for QNetworkReplyWrapper #11328
Conversation
Fix it by watching the QNetworkReply's destroyed() signal and avoid the dangling pointer instead. The QNetworkReply doesn't need to be aborted in this case anyway. Issue: ariya#11252 Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=116035
Good catch! I'll have a look and test it. |
Works for me. |
Awesome fix, it's landed now! Thanks @vitallium! |
I've tried building from this branch. I'm now getting this crash consistently, I think it's happening more often than the QObject::disconnect. Maybe this was a bug introduced? Mark Program received signal SIGSEGV, Segmentation fault. |
Could you please attach an example script? |
I see this branch has been merged. I've built from the master branch and I can't reproduce this crash (above). I think it was a bad build. |
Fix it by watching the QNetworkReply's destroyed() signal and avoid the dangling pointer
instead. The QNetworkReply doesn't need to be aborted in this case anyway.
Issue: #11252
Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=116035