Hey,
I'm a developer behind TouchDesigner, and we're getting a lot of reports from users these days that are unable to start our application at all, and the .dmp files are indicating the crash is occuring in graphics-hook64.dll in our main thread. We don't get any call stack information under that so we can't see what call from our side is getting into that binary and causing the crash.
Are there any .pdb files available to try to see where in that .dll the crash is occurring (and to allow unrolling the rest of the stack).
Is there any way to opt-out of that .dll getting injected into my process?
Thanks
Malcolm
I'm a developer behind TouchDesigner, and we're getting a lot of reports from users these days that are unable to start our application at all, and the .dmp files are indicating the crash is occuring in graphics-hook64.dll in our main thread. We don't get any call stack information under that so we can't see what call from our side is getting into that binary and causing the crash.
Are there any .pdb files available to try to see where in that .dll the crash is occurring (and to allow unrolling the rest of the stack).
Is there any way to opt-out of that .dll getting injected into my process?
Thanks
Malcolm