(It originally used H/W rendering.)Īlso, the problem did not occur when using the graphics card as a Geforce GTX1050. Like suggested in the community's reply( link), the memory leak issue didn't happen when running WPF app using S/W rendering in PC (1). ![]() Graphics: Intel(R) UHD Graphics 610 1GB.PC (2) - H/W configuration not occurring the issue (until Jan, 2023.) We concluded that this is the memory leak issue with new configuration as we haven't encountered this kind of issue with the same program in the previous configuration (until Jan, 2023) which is mentioned below: NET Framework 4.8.1.Īlso, I updated the graphics driver's version to 31.0.101.3790/31.0.101.2114 but the issue was not resolved. We've checked if there's any issue regarding Software memory leaks and have tried to figure out the issue by installing. Graphics: Intel(R) UHD Graphics 710 1GBĪ memory leak occurred in the WPF app running on every single PC with the configuration above.CPU: Intel Celeron(R) G6900 圆4, Core * 2. ![]() OS: Windows 10 IoT Enterprise LTSC 21H2.PC (1) - H/W configuration with the issue (since Feb, 2023.) ![]() We've been using the PCs with the following configuration since Feb, 2023 and we encountered the memory leak issue: These PCs run a KIOSK program developed with WPF. We have dealt with a number of PCs using the same H/W configuration. I would like to inquire about the memory leak issues we encountered when running a WPF full-screen (KIOSK) application in an environment using Intel UHD Graphics 710 (1GB).
0 Comments
Leave a Reply. |