Created by: onze
… when they have actually NOT timed out (were calling back into a deleted struct).
Old behavior:
- request without timeout on a responding url: get an answer back, works as expected.
- request without timeout on a non-responding url: get no answer back, no callback called, works as expected.
- request with timeout on a non-responding url: get no answer back, timeout gets triggered, works as expected.
- request with timeout on a responding url: get answer back, reply gets deleted, timeout gets triggered, callback writes on deleted data -> crash.
Patch content: replaced the timeout integer with a QTimer to handle and own the timeout callback. The timer is stopped whenever a call gets an answer back, or the owner object is deleted.
This has only been tested empirically since the patch has a small scope.
Copying the technical committee: @ravinikam @stkrwork @etherealjoy @MartinDelille @muttleyxd
Thank you