So the access violation actually occurs after the new file is closed. So maybe it is even with the underlying Windows function for closing windows? It seems to only happen when our application is maximized as well when opening the new file. And to be more specific the actual method call we are using is
Code:
int hResult = (int)ShellExecuteW(Application->Handle, NULL, objectPath.c_str(), NULL, NULL, SW_SHOWNORMAL);
It appears to happen more frequently when on a Windows 10 machine. It will happen on a Windows 7 machine but not nearly as often. It may sound silly too but if the access violation doesn't occur when first opening the new file I was able to get it to appear by spamming the maximize then restore down button of the window many times then closing the window when it's maximized.
Hopefully this helps, if there is anything else you need to know hopefully I can give you an answer.
Thanks!
Kevin