I agree with https://github.com/dotnet/try/issues/290#issuecomment-503768... - this seems pretty likely to be "you are using `print(...)` but don't have a custom one in scope, so it's calling the window's func"

It happens in Firefox too, fwiw. Probably just a mono.js flaw.