Threading issues after calling SA-MP natives

[SnowDog4822]

When attempting to use await in the current 0.8.0-alpha1 release on .NET Core 2.0 the method will not proceed past the await or complete. I tested this on both my own game mode and @ikkentim's TestMode. In both cases, any method using await will not complete.

When testing the TestMode in particular, this issue arose both with the /dialogtest command as well as a simple command that I wrote for testing purposes.

This command:

        [Command("testawait")]
        public static async void testAwait(BasePlayer player)
        {
            Console.WriteLine("Waiting 2 seconds...");

            await Task.Delay(2000);

            Console.WriteLine("Success!");
        }

resulted in only the Waiting 2 seconds... line being printed. The success message never printed.

I am unsure if this only affects .NET Core or .NET Core 2.0 in particular.

[ikkentim]

It works for me 🤔

Waiting 2 seconds...
Success!

Used your code on a fresh, .NET Core 2.0 project

[SnowDog4822]

I know I've already contacted you about this in Slack, but for the record I'll update this issue. This is apparently some sort of threading problem somewhere in the SampSharp.Core.Threading either with the MessageQueue or MessagePump and it can be reproduced by calling a native (such as SetGameModeText()) anywhere in the gamemode and then attempting to use async/await afterwards. Once the native has been called, it has a random chance (it doesn't reproduce 100% of the time) of hanging up all future asynchronous methods in the SampSharp server.