by rusty » Tue Oct 22, 2024 1:43 pm
Based on the dev team's preliminary assessment, this is a limitation of the debug build and slow closing of MM debug will always occur if dbgview isn't running with the debug build to capture messages.
The solution for now would be to switch to the 'regular' build once testing is complete, but we plan to examine this further in the future.
Thanks!
-Rusty
Based on the dev team's preliminary assessment, this is a limitation of the debug build and slow closing of MM debug will always occur if dbgview isn't running with the debug build to capture messages.
The solution for now would be to switch to the 'regular' build once testing is complete, but we plan to examine this further in the future.
Thanks!
-Rusty