DPP 4.16.11.0 frequently crashes

[dpp4user]

I'm using DPP 4.x for a long time (starting with 3.x long time ago) without stability problems and I'm regularly updating it.

However since I updated to 4.16.11 it frequently crashes while editing an image. It crashes randomly right after a mouse click to some widget. The Windows event log always shows a System.AccessViolationException by Dpp4Main.exe System.AccessViolationException
at Canon.Dpp.Dsf.DPPMWare+NativeMethods.DppMWProcessPreviewImageEx(IntPtr, DppRect, DppPreviewProcessAction, Int32, IntPtr, IntPtr, IntPtr ByRef)
at Canon.Dpp.Dsf.Image.Preview.DSFPreviewProcess.CreatePreviewImage()
at Canon.Dpp.App.Controller.DAPImageController.CreatePreviewImage(Boolean, Boolean)
at Canon.Dpp.App.Controller.DAPImageController+<>c__DisplayClass306_1.<PreviewProcessImageChanged>b__1()
...

which shows a software bug most probably in some of the DPP (native, probably C++ written) modules.

I also observed, less frequently, an access violation (0xc0000005) in Dpp4Batch.exe i.e. DppCoreSubD.dll

(For the software engineers among us: This strongly smells like UB.)

I'm editing compressed CR3 images from an EOS R6.

Does anybody else experience this problem?

How can I report this bug?

I'm going to check how to downgrade to an older DPP version and see whether it works again.

[jrhoffman75]

You can download 4.16.10 or 4.16.0 from the R6 support site.

Does your computer meet the minimum requirements identified for the software?

Does the issue happen with a regular .CR3 file?

[dpp4user]

I tried 4.16.10.0 and don't observe the crashes so far.
I cannot say whether it is the (downgraded) software version or the re-installation (that might have restored some settings that caused the random crashes).

[dpp4user]

Thats irony, just after I wrote the recent post, DPP (4.16.10.0) crashed as well (same traceback).

[jrhoffman75]

When I had issues with DPP4 (not what you are reporting) doing a Registry clean with free CCleaner resolved my problem. 

[wq9nsc]

A long time ago, I ran into a DPP random crash error that was resolved by using Windows to remove the old version and then doing a fresh install.

It has been several years since I have had a crash issue with DPP but I still see it turning into a memory hog and slowing down in long editing sessions; that is resolved by exiting and re-launching DPP. 

It doesn't matter that there is plenty of memory left for the system, it will still become very slow with memory bloat.  I am using a dual CPU HP workstation with 128 GB of RAM per CPU along with dual Nvidia workstation graphics cards with their own dedicated fast video RAM so only a small percentage of total RAM is used by DPP even in its maximum bloat state but once it climbs to 4 or 5 GB it noticeably slows.

My usage probably creates DPP conditions most won't see because this occurs when editing sports events photos where I am using three 1DX series bodies and often capture close to a thousand images between the three.  It might not run into this issue if the images from each body were in a separate directory for editing but because I often use more than one body during the same play I need the images editable in the specific time sequence in which they were captured.

Rodger