MP.TextLabels.New causes segfault

[Jan Altensen]

when using MP.TextLabels.New the server crashes with a segfault afterwards

        [Command("test")]
        public async Task test(IPlayer player)
        {
            MP.TextLabels.New(player.GetPosition(), "test", 0, Color.White);
        }

[Jan Altensen]

using MP.TextLabels.NewAsync words fine
nevertheless it shouldnt crash when using the non async method

#
# Fatal error in HandleScope::HandleScope
# Entering the V8 API without proper locking in place
#

Segmentation fault

[Nick Strohm]

Which branch are you using? Its quite interesting because the async method uses the sync method.

[Jan Altensen]

im using the latest release (V1.2.0) on windows

[Nick Strohm]

Try wrapping the sync New call inside a MP.Schedule call. Rage requires mostly everything to happen in the main thread. The async method wrapps the synced method inside a MP.Schedule call.

[Jan Altensen]

wrapping MP.Utility.Schedule around it works fine
await MP.Utility.Schedule(() => MP.TextLabels.New(player.GetPosition(), "test", 0, Color.White));

[Tim]

This seems to be affecting the entire sync API, not just textlabels.

[Francesco Paolocci]

To give you a general rule regarding async/sync calls:

Async API: Directly and always safely usable. Those calls are already with MP.Utility.Schedule wrapped sync API calls.
Sync API: Must be used within MP.Utility.Schedule. We offer those sync methods to reduce overhead on your side and to group batches of calls together.

See V1.2.0 changelog