[Webkit-unassigned] [Bug 181138] [GTK] Crash destroying WebCore::FileMonitor

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=181138

Carlos Garcia Campos <cgarcia at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bfulgham at webkit.org,
                   |                            |cgarcia at igalia.com,
                   |                            |wilander at apple.com

--- Comment #4 from Carlos Garcia Campos <cgarcia at igalia.com> ---
I can't reproduce this, but I think we can avoid all race conditions by always creating and destroying the platform file monitor in the work queue thread synchronously. 

However, I wonder if we should revert the patch that added support for resource load stats in the glib based ports. Does it make sense to have it without the machine learning part? The layout tests were passing when we added the support, but that's no longer the case, all of them are timing out now and John skipped them in r223253.

We should fix FileMonitor in any case, because even if it's only used by resource load stats right now, it's a generic implementation that could be used by other parts eventually.

-- 
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/20180102/49bbdcc7/attachment.html>