Bugfix: ProfileExporter.JSON - gracefully handle managed allocations coming from native runtime - Emit "<mono-native-runtime>" if we don't have managed callstack Finally caught it - this can happen when mono tries to invoke a managed callback which requires a managed allocation (the callback accepts string[], for example) as a first method in managed code. Was able to repro in editor due to it's script compilation callbacks. Tests: triggered perfsnapshot 40 times without issues