Capture stack traces at top level vs doing frame-skipping arithmetic. I think this is actually mandatory as I was seeing some strange logging behavior on Windows Headless that I can only explain if .NET was inlining method calls, which obviously would ruin my "skip 4 frames" style of arithmetic.
Stop intercepting internal .NET calls to AppDomain.GetAssemblies(). It turns out that .NET calls this a lot internally, and my logic that was supposed to be intercepting FrooxEngine calls was also messing with internal .NET calls not initiated by FrooxEngine. I've implemented a smarter stack frame search to solve this.
This does the following:
AppDomain.GetAssemblies(). It turns out that .NET calls this a lot internally, and my logic that was supposed to be intercepting FrooxEngine calls was also messing with internal .NET calls not initiated by FrooxEngine. I've implemented a smarter stack frame search to solve this.