Windows Application Error 0xc0000005 in 3D Object Tracking

gonna pin this other thread here.

Digging into the issue from the memory side, it appears this is still an ongoing thing, and fortunately (for me), 3D Object Tracking does not require the Tracking ParametersEnable Tracking option to be enabled. With it off, the app no longer grows indefinitely. Going to drop new builds on our test boxes and see if we get longer & more stable runtime.