the PlayerLoop internal function has been called recursively

Will the use of environment.stacktrace in the application.logmessagereceived callback function cause the problem of circular reference?

logmessagereceived already provides stacktrace in the second parameter, so no point in calling it.

Calling Environment.stacktrace shouldn’t cause any issues as it shouldn’t call player loop due to being part of C#/MS API and not part of unity.