[mono] bug about wasm single thread using lock

[srxqds]

we found the object interop between js and c# excecute slowly
you can find below flame graph:

the AssertNotDisposed take most time of argument transfer.

we use single thread, Is it not necessary using lock at below functions :

runtime/src/libraries/System.Runtime.InteropServices.JavaScript/src/System/Runtime/InteropServices/JavaScript/JSObject.References.cs

Lines 48 to 54 in da4f0a3

	internal void AssertNotDisposed()
	{
	lock (ProxyContext)
	{
	ObjectDisposedException.ThrowIf(IsDisposed, this);
	}
	}

runtime/src/libraries/System.Runtime.InteropServices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Marshaling/JSMarshalerArgument.Task.cs

Lines 41 to 50 in da4f0a3

	public unsafe void ToManaged(out Task? value)
	{
	// there is no nice way in JS how to check that JS promise is already resolved, to send MarshalerType.TaskRejected, MarshalerType.TaskResolved
	if (slot.Type == MarshalerType.None)
	{
	value = null;
	return;
	}
	var ctx = ToManagedContext;
	lock (ctx)

should it wrapper with FEATURE_WASM_MANAGED_THREADS as other function do.

internal void AssertNotDisposed()
        {
#if FEATURE_WASM_MANAGED_THREADS
            lock (ProxyContext)
#endif
            {
                ObjectDisposedException.ThrowIf(IsDisposed, this);
            }
        }

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

[srxqds]

anyone can take time to figure out this?

[pavelsavara]

It seems legit, I will get to it eventually.