The Component Dispose is not safe in lock

[lindexi]

Description

The System.ComponentModel.Component will lock self when enter Dispose. Maybe there will be dead locks in this approach.

    protected virtual void Dispose(bool disposing)
    {
        if (disposing)
        {
            lock (this)
            {
                _site?.Container?.Remove(this);
                if (_events != null)
                {
                    ((EventHandler?)_events[s_eventDisposed])?.Invoke(this, EventArgs.Empty);
                }
            }
        }
    }

Other information

The mini demo: https://github.com/lindexi/lindexi_gd/tree/5219a17e96a3577639d0b486c57bc699941c585b/HearwhejiyehallyiheFubaduwheefu

        var component = new Component();
        lock (component)
        {
            Task.Run(() => component.Dispose()).Wait(); // dead lock
        }

Run the code, and then you will find that the thread never exits

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @safern
See info in area-owners.md if you want to be subscribed.

[ericstj]

Not a regression: Same behavior in desktop. Certainly it's not best practice to lock on public objects but given this behavior has been around for decade+ I'm reluctant to change it as it may be part of the design to have a shared lock object between this type and implementers (for example in WinForms).

WRT to the repro: it hangs when you lock on it; don't do that :) Do you have any real world scenario that's blocked by this behavior?

[lindexi]

Do you have any real world scenario that's blocked by this behavior?
@ericstj No

Although this question may be used as a feature, should we add some comments or documentation to tell future developers?