Exported app crashes with EGL display error after running for 8 hours

vvvv gamma bug
1

Helloo

I have troubles with an exported app made with stable 7.0 when it runs for more than 8 hours.
Everything runs correctly and smoothly but at some point (in the middle of the night), I get an EGL display error:

2026-02-11T01:56:40.0416956+01:00  \[FTL\] \[{ SourceContext: “jen_sectorcoupling” }\] Failed to initialize EGL display from device (e37a2f09)
VL.Skia.Egl.EglException: Failed to initialize EGL display from device
at VL.Skia.Egl.EglDisplay.FromDevice(EglDevice angleDevice)
at VL.Stride.SkiaRenderer.DrawCore(RenderDrawContext context)
at Stride.Rendering.RendererBase.Draw(RenderDrawContext context)
at VL.Stride.Rendering.GraphicsRendererGroup.Stride.Rendering.IGraphicsRendererBase.Draw(RenderDrawContext context)
at VL.Stride.Rendering.GraphicsRendererGroup.Stride.Rendering.IGraphicsRendererBase.Draw(RenderDrawContext context)
at VL.Stride.Rendering.EntityRendererRenderFeature.Draw(RenderDrawContext context, RenderView renderView, RenderViewStage renderViewStage, Int32 startIndex, Int32 endIndex)

Seems to be a graphic driver issue, but my Nvidia driver is already up-to-date.

I saw this post and this one mentionning LibEGL.dll and LibGLESv2.dll.

When I check properties of the 2 exported dlls, I get the correct ANGLE ones:

libEGL
libEGL405×509 12.4 KB

libGLESv2
libGLESv2405×509 12.1 KB

I don’t think it is smart to replace those 2 files with ones from a previous Gamma version (6.7 or 6.6) and it said to be fixed for 7.0. But should I?

Also, nothing to report from Windows Event Viewer.

Anyone experienced this also on 7.0?
Could it be related to a memory leak?

2

Yes we had the problem constantly on a project last year. We had TeamViewer running and removing it entirely from the computers stopped the EGL error.

But then it appeared again, for some reason we couldn’t identiy this time. There is a fix made by @Elias on some recent preview.

3

I don’t have TeamViewer on the computer but I just removed OBS. Maybe it also does something.

Otherwise, there is nothing on the machine except from vvvv, git, git extensions, vs code, helix p4merge and .NET. So pretty much nothing, and only the stuff I really need.

I tested on a second machine yesterday, and it runs correctly on that one.
So, it seems to be related to that computer specifically.

I am logging now all the info about the graphic card when the application runs to try to identify if anything wrong is happening.

Thanks @lecloneur for pointing out that you found a fix on a recent preview. I will also run it on a preview version to check if it happens again.

4

Do you have the same GPU driver version? Studio drivers or GameReady drivers? Same GPU?

5

It is not the same GPU but it is the same GPU driver version.

GPU Info Computer 1 (Not Working) Computer 2 (Working)
GPU model Nvidia GeForce RTX 5070 Ti Desktop Nvidia GeForce RTX 3080 Laptop
GPU Driver Studio 591.74 Studio 591.74
Dedicated GPU Memory 16GB 8GB
GPU Memory (dedicated + shared) 33,9GB 15,7GB
6

Let me wrap up my latest tests and how I resolved this issue on my side, in case someone encounters this in the future, there might be some useful information. Who knows?

  1. I tested my application on a second machine with identical hardware.
    → Result was the same: it crashed after approximately 8 hours with the same EGL Display error.

  2. I ran GPU-Z and logged all the info about the GPU.
    I could see that just before the application crashed, the GPU Load and Board Power Draw dropped by half.
    → I suspected a power-saving mode to be activated somewhere, even though I set High Performance mode.

  3. I checked again that everything was set to High Performance mode.
    One thing to add: in the new Windows 11 Settings, it is not enough to set High Performance mode here. You also have to go to the former Control Panel, then Power Options, and set High Performance here too. For whatever reason, setting it only in the Windows 11 Settings does not set it in the Power Options..
    My app in Nvidia Control Panel was also already set to High Performance.
    → Nevertheless, it did not solve the issue.

  4. I tried Gamma 7.1-preview, as suggested by @lecloneur. I thought it was solving my issue as my app ran for 24 hours without trouble but then, boom, it crashed again.
    → Better result with export made with 7.1-preview, but error was still happening after some time. This could be enough if the computer is restarted every day, but maybe it could also happened earlier..

  5. I performed a clean Windows 11 Pro installation on the machine, and ran the application again.
    → Did not solve anything.

  6. In the meantime, I was running the application on the laptop with the RTX 3080 for 3 days in row without trouble.
    → I was confident my application was not the issue here, but that it was related to the other computer / hardware.

  7. After multiple tests, I started to get some new “information” in Windows Event Viewer: Windows tried to start Windows Search and it failed with a fatal error just before my application crashed. I disabled Windows Search service, and increased the pagefile.sys file. Before that, I could see that the size of that file was very low on the machine compared to the other ones I was using, even with Windows adjusting itself the size.
    → I got a improvement by a few hours. But at some point, it was still crashing.

  8. At this point, I could live by using the 7.1-preview and the extended pagefile.sys
    I wanted to do one last test: flashing the BIOS.
    And, BINGO!
    → My app ran for multiple days in a row without trouble after doing so.

I usually do not try to flash the BIOS, that’s why I did it at the very end of my tests.
In my case, it solved the issue, but I would suggest you to make some tests before doing it, as it is still risky.
There is probably a fix which do not requires you to flash it.