artemist/yuzu
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

core: Initialize cheats after load to avoid VMManager crash

Browse source 
This used to occur due to the VMManager being nullptr at the time cheats were registered (during load, but before it was done). This is bypassed by not accessing the VMManager for offset data until load is complete,
This commit is contained in:
Zach Hilman 2019-05-30 19:37:18 -04:00
parent 37850eeee5
commit 3e729c13cc
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
src/core/core.cpp
View file

@ -205,6 +205,11 @@ struct System::Impl {
gpu_core->Start(); gpu_core->Start();
cpu_core_manager.StartThreads(); cpu_core_manager.StartThreads();
// Initialize cheat engine
if (cheat_engine) {
cheat_engine->Initialize();
}
// All threads are started, begin main process execution, now that we're in the clear. // All threads are started, begin main process execution, now that we're in the clear.
main_process->Run(load_parameters->main_thread_priority, main_process->Run(load_parameters->main_thread_priority,
load_parameters->main_thread_stack_size); load_parameters->main_thread_stack_size);