Crash with W10 update 10.0, Build 19042

[vastempty]

It has been suggested that it is an memory issue with .NET and to downgrade to an earlier version, which you can not do in windows 10.

11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 CPUs), ~2.4GHz
Installed RAM 16.0 GB (15.8 GB usable)
System type 64-bit operating system, x64-based processor

New laptop dedicated to UCCNC
Windows 10 Home 64-bit (10.0, Build 19042) (19041.vb_release.191206-1406)
.NET 4.8

The .NC file is too large for the forum upload, but I can send if you want to repro this issue with a new build\install of windows. Although the crash happens with any largish file I try.
UCCNC rumbles along till it runs out of memory.
There is another bug report 01/13/22 with this same issue "Memory leak when file is open". No resolution there either.

Log Name: Application
Source: .NET Runtime
Date: 1/20/2022 3:08:14 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Garage
Description:
Application: UCCNC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at OpenTK.Graphics.OpenGL.GL.BufferData[[OpenTK.Vector3, OpenTK, Version=1.1.0.0, Culture=neutral, PublicKeyToken=bad199fe84eb3df4]](OpenTK.Graphics.OpenGL.BufferTarget, IntPtr, OpenTK.Vector3[], OpenTK.Graphics.OpenGL.BufferUsageHint)
at UCCNC.Makedrawing.changeverticescolor(Int32, Int32)
at UCCNC.Form1.screenrecolorcycle_real()
at UCCNC.Form1.GLtimer_Tick(System.Object, System.EventArgs)
at System.Windows.Forms.Timer.OnTick(System.EventArgs)
at System.Windows.Forms.Timer+TimerNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at UCCNC.Program.Main(System.String[])


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-01-20T22:08:14.8521744Z" />
<EventRecordID>2132</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Garage</Computer>
<Security />
</System>
<EventData>
<Data>Application: UCCNC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at OpenTK.Graphics.OpenGL.GL.BufferData[[OpenTK.Vector3, OpenTK, Version=1.1.0.0, Culture=neutral, PublicKeyToken=bad199fe84eb3df4]](OpenTK.Graphics.OpenGL.BufferTarget, IntPtr, OpenTK.Vector3[], OpenTK.Graphics.OpenGL.BufferUsageHint)
at UCCNC.Makedrawing.changeverticescolor(Int32, Int32)
at UCCNC.Form1.screenrecolorcycle_real()
at UCCNC.Form1.GLtimer_Tick(System.Object, System.EventArgs)
at System.Windows.Forms.Timer.OnTick(System.EventArgs)
at System.Windows.Forms.Timer+TimerNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at UCCNC.Program.Main(System.String[])

</Data>
</EventData>
</Event>

Faulting application name: UCCNC.exe, version: 1.0.0.0, time stamp: 0x5e3845b5
Faulting module name: ig12icd64.dll, version: 27.20.100.9466, time stamp: 0x6062e276
Exception code: 0xc0000005
Fault offset: 0x00000000000a2d59
Faulting process id: 0x78c
Faulting application start time: 0x01d80e369601da47
Faulting application path: C:\UCCNC\UCCNC.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_bf22c341d1c71ba2\ig12icd64.dll
Report Id: ab8953f2-ef8f-4255-a953-30f6cbb62ad2
Faulting package full name:
Faulting package-relative application ID:

[cncdrive]

Yes, it looks like somekind of OpenGL memory issue.
And yes, please send the file in email or upload it to Google drive or something like that and tell us the link.

[vastempty]

https://we.tl/t-G1tfj9U2Mm

[cncdrive]

I tested and your file loads fine on my computer.

[ger21]

Loads fine for me too. Takes about 8 seconds.

[eabrust]

Also loads fine for me as well on my office laptop (demo mode), Win 10, 16gb ram. Video is Nvidia M3000M

I'm letting it run the file , but so far after 20 minutes, CPU usage is nothing (~5%), used memory is ~490-500 Mb, and GPU load is 13-15%, and hasn't budged since opening or starting to run the file.

How long did it take for you to get the exception? Seems like a better question about your laptop would be what is the graphics card/chip, and how much memory on it, and do you have the latest/best drivers for it.

regards,
Eric

[eabrust]

Out of curiosity, I opened the file with a few of my shop computers (small form factor HP elitedesk pcs)

Computer 2 is an i7, intel 530 graphics, 8gb ram, win10 19043.1466. File opened quick, no crash, memory usage went to approx 830mB, no change after waiting and running file. After 20 minutes, memory use has stayed put:

Computer 3 is an i5, intel 530 graphics, 8gb ram, win10 19042.1466. File opened quick, no crash, but memory usage climbs to > 5-6GB. I've let it run the file, and no crash yet, but memory usage is very weird, it will climb high, then will suddenly drop to 500mB then climb right back up to >5-6GB over the course of about a minute or two.

Between the two PCs, other than i5 vs i7 they both have different graphics drivers installed for the same intel 530 chipset. The computer with the memory issue has a newer version of the intel driver (27.20.100.9416) than the computer that behaves nicely (27.20.100.8681). I'm not willing to update the driver to find out if it makes my #2 computer act poorly

I'll let all three computers run the program to the end to see if any of them crash, but only one seems to be behaving in such a way it may crash.

regards,
Eric

[cncdrive]

We've tested the UCCNC with much much larger files, so the file size should not explain the problem.
It could be an OpenGL/graphics driver problem of the graphics card in the computer or maybe a bug in the OpenTK library related to a graphics card's issue. (However I have never seen one which could cause a crash.)

[vastempty]

Sorry, its not loading the file, its running it. Demo mode fails for me.

Not sure how far it gets (at least halfway) before the exception is thrown.

eabrust, thanks for running it. What I noticed is right away the running program allocated 14GB out of my available 15.8GB, and bounced along the top until the exception.

Slightly different version driver:
Card name: Intel(R) Iris(R) Xe Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) Iris(R) Xe Graphics Family
Driver Version: 27.20.100.9466
Directx 12
OPenGL: 4.6.0

So my bug is similar to bug report "Memory leak when file is open" opened on 1/13, except it takes awhile to crash.


Thanks,

[vastempty]

Re-running test, it actually allocated 6.8GB then grew quickly to 15GB, and bounced around there until the exception.