Nah, the stack dump is inaccurate (happens with minidumps if it crashes in library or OS code and the dump reader cannot resync stacks correctly due to lack of frame pointers). The fragment it claims to be on the stack shows it calling espionage functions from CvUnit::isInViewport() which never happens (there are no such calls). This is just the result of old stack frame fragments remaining in memory within the current stack frame - it basically means we cannot tell anything rom the minidump.
Good to know then.