[Webkit-unassigned] [Bug 201871] New: AbortSignal does not always emit the abort signal
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Sep 17 06:32:03 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=201871
Bug ID: 201871
Summary: AbortSignal does not always emit the abort signal
Product: WebKit
Version: Safari 12
Hardware: Macintosh
OS: macOS 10.14
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jkieboom at esri.com
This problem occurs in a large code base and I am having trouble setting up a simple reproducible test case outside of our application. It looks like when using an AbortController, calling abort on it may in certain circumstances not emit the abort event on the corresponding signal. It feels like this is problem of premature garbage collection because if I plug the corresponding signal on another object that is kept alive, I do receive the abort event correctly. In addition, the problem in our application does not appear if I use an AbortController/AbortSignal shim (further indicating that this is a problem in the native implementation somehow). I'll try to come up with an isolated test case, but I'm having a hard time doing so.
--
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/20190917/9ffcce3d/attachment-0001.html>
More information about the webkit-unassigned
mailing list