Home → WINDEV 26 → WinDev 26 - Problem with Charts and newest Windows 10 Updates
WinDev 26 - Problem with Charts and newest Windows 10 Updates
Started by Claudio Kirchmair, Nov., 25 2021 10:26 AM - No answer
Posted on November, 25 2021 - 10:26 AM

We currently have the latest WinDev 26 update (WINDEV 26 - Update 1 (01A260101d) | October 06, 2021) and we always create a 64-bit EXE. Recently we run into the following problem on various Windows Versions after closing our program after it loaded a window with a Chart (it doesn't matter what settings you made for that chart):

Windows "Event Viewer"
Faulting application name: SanoCon DEV 18.exe, version: 26.21.5019.3, timestamp: 0x6091938c
Faulting module name: wd260vm64.dll, version: 26.0.480.22, timestamp: 0x6142074d
Exception code: 0xc0000005
Error offset: 0x00000000000831c5
Faulting process id: 0x4f0
Faulting application start time: 0x01d7e120c938479f
Faulting application path: C:\My Projects\SanoCon DEV 26\Exe\64-bit Windows executable\SanoCon DEV 18.exe
Path of the faulty module: C:\My Projects\SanoCon DEV 26\Exe\64-bit Windows executable\wd260vm64.dll
Report ID: 0f089a48-fad1-43bc-9213-504b17835b26
Full name of the faulty package:
Application ID relative to the failed package:

This is not a problem on the new Windows computers (Windows 10, Windows Server 2019) because the error is intercepted in the background. But it is visible in the Windows "Event Viewer" if you look into "Applications". After closing the program, our customers get a Windows error message like "SanoCon DEV 18 has caused an error ...". If a customer has a new version of Windows, he does not see the error.

Our observation is that after closing the program something is still loaded in the background for about 3 seconds (visible from the fact that the mouse pointer shows the running circle). And that only happens when a chart was in the window. We completely deleted the chart from the window and suddenly the error was gone. If I create a new default chart using the WinDev Editor and save the window, then the error is there again (without anything else being done here). What I also noticed is that the error does not occur in debug mode.

Has someone else encountered this problem before? We also get the same problem with WinDev 25 applications which aren't currently developed.