V1: MainLoop.Invoke causes 1 CPU core consumption on Linux and macOS

[AndreyAkinshin]

Describe the bug
After the first call of MainLoop.Invoke, the application starts consuming 1 CPU core (100%) on Linux and macOS.

To Reproduce
Steps to reproduce the behavior:

1. Install .NET SDK 8.0.100 on Linux or macOS
2. Create a new .NET 8 Console Application: dotnet new console -f net8.0
3. Install Terminal.Gui 1.14.1: dotnet add package Terminal.Gui --version 1.14.1
4. Put the following code in Program.cs:

using Terminal.Gui;

Application.Run<MyWindow>();
Application.Shutdown();

public class MyWindow : Window
{
    public MyWindow()
    {
        Application.MainLoop.Invoke(() => { });
    }
}

5. Run the program: dotnet run
6. Check out the processes with the highest CPU usage: ps -eo pid,%cpu,command -r | head
7. You should see your freshly running application with CPU usage of ~100%

Expected behavior
MainLoop.Invoke should not cause stable CPU usage. Before the first call of MainLoop.Invoke, the application CPU usage is quite low, which is also the expected behavior for the application after this call.

Environment
OS: Linux, macOS
Checked Terminal.Gui versions: 1.13.5, 1.14.1
Checked .NET versions: 7.0.14, 8.0.0

Screenshots
I have used Rider to get a dotTrace performance snapshot. Here are the corresponding screenshots:

Timeline:

Tracing:

[tig]

Can you please try to repo this using v2? https://www.nuget.org/packages/Terminal.Gui/2.0.0-pre.210

[AndreyAkinshin]

@tig I have checked v2.0.0-pre.210 on macOS, everything works nice with no CPU noise.

A note: I have used Application.Invoke(() => { }); instead of Application.MainLoop.Invoke(() => { }); since MainLoop is internal in v2.

[AndreyAkinshin]

@tig just to clarify the issue state: do we have a fix for this problem in 1.x or is there no plan to fix it in 1.x?

[tig]

@tig just to clarify the issue state: do we have a fix for this problem in 1.x or is there no plan to fix it in 1.x?

Sorry, I misunderstood. I thought you were ok on v1. Reopening.