WorkerCacheStorageConnection should handle the case of terminated workers
Created attachment 328203 [details] Patch
Comment on attachment 328203 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=328203&action=review > Source/WebCore/ChangeLog:14 > + Added a method to check a worker thread is still valid. That type of technique won’t work 100% perfectly. It’s possible that the thread has been fully deleted, but then a new thread allocated, and the new one is in the same memory so happens to have the same address.
Comment on attachment 328203 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=328203&action=review >> Source/WebCore/ChangeLog:14 >> + Added a method to check a worker thread is still valid. > > That type of technique won’t work 100% perfectly. It’s possible that the thread has been fully deleted, but then a new thread allocated, and the new one is in the same memory so happens to have the same address. I guess I could further check the thread id if the pointer is still alive.
Created attachment 328352 [details] Patch
Patch appears to fix the crash for me locally.
Comment on attachment 328352 [details] Patch Clearing flags on attachment: 328352 Committed r225481: <https://trac.webkit.org/changeset/225481>
All reviewed patches have been landed. Closing bug.
*** Bug 180337 has been marked as a duplicate of this bug. ***
<rdar://problem/35831955>