Pokechu22 9e0755a598 HookableEvent: Use std::recursive_mutex instead of std::mutex
This fixes a crash when recording fifologs, as the mutex is acquired when BPWritten calls AfterFrameEvent::Trigger, but then acquired again when FifoRecorder::EndFrame calls m_end_of_frame_event.reset(). std::mutex does not allow calling lock() if the thread already owns the mutex, while std::recursive_mutex does allow this.

This is a regression from #11522 (which introduced the HookableEvent system).
2023-04-02 15:51:21 -07:00
..
2022-12-10 11:20:23 +01:00
2023-03-02 19:54:15 -06:00
2022-01-02 14:39:34 -08:00
2022-08-28 22:38:35 -07:00
2022-01-02 15:36:47 -08:00
2023-01-10 05:17:43 -08:00
2023-02-17 16:58:24 +01:00
2022-04-12 12:28:57 -07:00
2022-07-25 18:32:16 -07:00
2022-07-25 18:40:12 -07:00
2022-02-16 20:09:38 +00:00
2022-02-16 20:09:38 +00:00
2022-11-17 17:54:06 -05:00
2023-02-28 20:29:46 +01:00
2023-02-28 20:29:46 +01:00
2021-12-10 14:49:57 -08:00
2022-01-09 12:43:11 -08:00