Directx 11 update windows 10 64 bit7/19/2023 It seems noteworthy that that this leak occurs with both Nvidia and Intel video. I can say that the memory allocation failures start once I reach about 2 GB of available physical memory when running with the Nvidia card we use, and when running on the motherboard’s onboard Intel video the system can run until the memory drops much lower. I’ve tried some variations in order to isolate the problem, and I can go into more detail on these if necessary. So of course, my questions are whether anyone else seen this behavior and if so, what was wrong and how can it be fixed or at least mitigated? I certainly can see how an application could leak memory while it is running, but what seems unusual about this is that this memory is not recovered after the executables exit. We then found that as they open and close, the amount of “available physical memory”, as returned by the GlobalMemoryStatusEx function, is constantly shrinking. After stress-testing by rapidly opening and closing the small executables for several weeks, they started failing to open due to memory allocation failures. We recently started changing approaches and building and executing smaller individual DirectX 11 executables which open and close repeatedly rather than one large executable that just runs once. We run our kiosk system on a 64-bit Windows 10 system with 8 GB of memory and no swap file.
0 Comments
Leave a Reply. |