core_timing: request the timer thread's stop before waking it

CoreTiming::Reset set pause_event and event, and only then requested the
stop. The woken timer thread could take the wake-up, still see no stop
request, and go back to waiting on pause_event for good; the join that
follows then hung the frontend while booting a game ("Not Responding",
main thread in CoreTiming::Reset -> std::thread::join). Request the stop
first, so the thread sees it whenever it wakes.

0 files changed, 0 insertions, 0 deletions