[Bug 45642] Chrome/ Chromium sandbox needs x86-64 syscall thunks to match Windows

https://bugs.winehq.org/show_bug.cgi?id=45642

--- Comment #16 from Zebediah Figura  ---
(In reply to Fabian Maurer from comment #15)
> Ah, so the user update thread is only started when that structure is
> accessed, did I get that right?
>
> Can't we just start the thread when the timestamps are accessed? Or is there
> some technical reason we need to start the thread even when accessing some
> other part of the structure?

The way we can tell when the thread is started is by marking the page no-access
and then setting a SEGV handler. That would also be expensive.