Control crashes when no display is connected

[xhuan8]

var settings = new GLWpfControlSettings
        {
            MajorVersion = 2,
            MinorVersion = 1
        };
        OpenTkControl.Start(settings);

After upgrade from 4.2.3 to 4.3.3, I got AccessViolationException at startup randomly, which crashes my application.
The version is related to GLWpfControl or anything else? Should I change it to MajorVersion = 4?

Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is ofter an indication that other memory is corrupt.
Stack:
at OpenTK.Windowing.GraphicsLibraryFramework.GLFWNative.glfwGetVideoMode(OpenTK.Windowing.GraphicsLibraryFramework.Monitor*)
at OpenTK.Windowing.GraphicsLibraryFramework.GLFWNative.glfwGetVideoMode(OpenTK.Windowing.GraphicsLibraryFramework.Monitor*)
at OpenTK.Windowing.GraphicsLibraryFramework.GetVideoMode(OpenTK.Windowing.GraphicsLibraryFramework.Monitor*)
at OpenTK.Windowing.Desktop.NativeWindow..ctor(OpenTK.Windowing.Desktop.NativeWindowsSettings)
at OpenTK.Wpf.DDxGlContext..ctor(OpenTK.Wpf.GLWpfControlSettings)
at OpenTK.Wpf.GLWpfControlRenderer..ctor(OpenTK.Wpf.GLWpfControlSettings)

[NogginBops]

The version is related to the OpenGL version you want to request.

I've never seen this crash before...
What GPU are you running on?

[xhuan8]

The PC has 2 RTX 3090 installed.

[NogginBops]

Does the computer have a display or is it "headless"?

[xhuan8]

It connect to a monitor switch, when launching the program, monitor was switched to the other computer.
So it has no display at the moment.

[NogginBops]

Yeah it seems like we have an assumption in the NativeWindow ctor that there would always be a primary monitor which is causing this crash. I've opened this PR opentk/opentk#1820 to track the issue.

The only workarounds I see are either connecting a monitor to the computer or attaching something like a virtual screen or a dummy HDMI dongle.