[Webkit-unassigned] [Bug 191650] [Curl] Bug fix on Curl Request Scheduler.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 12 01:04:28 PDT 2019


Takashi Komori <Takashi.Komori at sony.com> changed:

           What    |Removed                     |Added
                 CC|                            |Takashi.Komori at sony.com

--- Comment #1 from Takashi Komori <Takashi.Komori at sony.com> ---
CurlRequestScheduler uses CURL pointer as job identifier, but libcurl sometimes re-use released pointer.
Therefore depending on timing, finalizeTransfer might be called more than once.

1)One CurlRequest (request A) is canceled and releases CURL* (pointer P).
2)And another CurlRequest is created (request B) and gets re-used CURL* (pointer P) same to former .
3)CurlRequestScheduler does finalize task for request A using pointer P.
4)When request B is closed, CurlRequestScheduler does finalize task using same pointer P and issue occurs.

Scheduler has to control tasks by CurlRequest* instead of CURL*.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190412/579efdb2/attachment-0001.html>

More information about the webkit-unassigned mailing list