DXFeedSubscription critical failure when calling GetSymbols() in .NET 9

[aaronwJordan]

Hello,

After a painful amount of time and troubleshooting, I have narrowed down an issue I ran into two weeks ago:

CLR: Assert failure(PID 40324 [0x00009d84], Thread: 38864 [0x97d0]): !"Attempt to execute managed code after the .NET runtime thread state has been destroyed."
    File: D:\a\_work\1\s\src\coreclr\vm\ceemain.cpp:1799 Image:
C:\dev\foo\api\bin\Debug\net9.0\api.exe

Besides just the error above spitting out into the debug console, you will also get a fail fast exception dialog that is hard to miss. I thought it may have been timing issues with various background threads accessing my DXFeedSubscription but sure enough after downgrading back to .NET 8 the issue goes away.

The issue occurs after several minutes (typically 2-5min) of repeatedly calling (my timer is on a one second interval) .GetSymbols().

Thanks!

[stdcion]

Hello @aaronwJordan!

I apologize for the late reply, but our support team does not monitor GitHub and expects requests to be submitted at https://jira.in.devexperts.com/servicedesk/customer/portal/1.

In any case, I tried reproducing this on .NET 9, left the code running all night, and didn’t encounter any exceptions.

    public static void Main(string[] args)
    {
        Console.WriteLine($"Current .NET Version: {Environment.Version}");
        Console.WriteLine($"Runtime Framework: {System.Runtime.InteropServices.RuntimeInformation.FrameworkDescription}");
        var symbols = new InstrumentProfileReader()
            .ReadFromFile("https://tools.dxfeed.com/ipf?TYPE=STOCK", "demo", "demo")
            .Select(instrument => instrument.Symbol)
            .ToList();
        var sub = DXFeed.GetInstance().CreateSubscription(typeof(Quote));
        sub.AddEventListener(events => { });
        sub.AddSymbols(symbols);
        while (true)
        {
           Thread.Sleep(1000);
           Console.WriteLine( sub.GetSymbols().Count);
        }
    }

Can you please advise me if I still need to change something in the code? Or maybe should I use a specific version of .net 9 (now i use v9.0.7)?

[stdcion]

Hello @aaronwJordan!

This is indeed a bug that occurs in .NET starting from version 9.0.5 through 9.0.7 (inclusive).
As a workaround, you can use version 9.0.4 of the .NET

I also opened an issue in the dotnet/runtime repository, and the issue will most likely be fixed starting with version 9.0.8 (has not yet been released).

From our side, I'll try to find a workaround so we don't have to wait for the fix. Perhaps we can use a different approach.