Bug editing small b&W imige V8 Windows

DxO PhotoLab
1

Open, paste, preset b& W- structured, spot Weighted and Internal error(failed on the Execute stage)

IMG_0628
IMG_0628480×640 97.6 KB

Only way to close is Task Manager. Deleted dop and catalogue did it number of times.

image
image905×336 57.5 KB

Last time allowed closing, Windows error log but no PL one

Faulting Application Path: C:\Program Files\DxO\DxO PhotoLab 8\DxO.PhotoLab.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: DxO.PhotoLab.exe
Problem Signature 02: 8.0.19977.417
Problem Signature 03: dc1a3bbd
Problem Signature 04: DxONET.CorrectionEngine
Problem Signature 05: 8.0.19977.417
Problem Signature 06: 66e187e7
Problem Signature 07: 16a5
Problem Signature 08: 2
Problem Signature 09: System.NullReferenceException
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 4354
Additional Information 2: 435482d30722f29daf475b85c4cc8253
Additional Information 3: 4a09
Additional Information 4: 4a098ff5402d9d4643dc0a395395359b

2

@John7 , you might want to address this with a ticket to support.dxo.com (see lower end of the page)

If you share the original file, some of us could see how it acts on our computers.

3

The original is the first imige, as said its small. Going to use at brothers wake!

4

Played around with the file in DPL and had no ill effects.
Metadata of the file is basically absent:
IMG_0628.jpg-MD.txt (1.4 KB)

(DPL 8 on macOS 14.7 on iMac 2019)

5

I followed you instructions and had the same issue. I had no problems closing PhotoLab normally and restarting it, and don’t seem to have any other issues. I just tested again with a different image and the problem occurred again as soon as I attempted to apply spot weighted Smart Lighting. I am using Windows 10 with all updates.

Mark

image
image1920×1453 106 KB

6

Will pass it on as a bug Monday

7

I edited my text above. I performed a second test with another image with the same results as soon as I selected Spot Weighting. I was able to switch to other images and continue editing. Most definitely a bug. I also tried with a few other images and the problem did not reoccur with them. DxO may need your original image to identify the problem.

Mark

8

The ‘Correction failed on the Execute stage’ error is also reproducible with PL8.0/Win11, latest patches/drivers, including NVIDIA Studio. However, PL does not hang in my case and I can continue editing. I’ve never seen it before with PL7/PL8, although I used SmartLighting Spot Weighted for thousands of RAW files. Just tried it with PL8 and several other jpegs, the smallest was 1086 x 1536 - got no error, it works. Maybe the problem is specific to very small RGB files only (under 1mpx?).

PhotoLab log contains among others:

DxOCorrectionEngine - Warn | DxO::FaceDetector_CorrectionInterface::Execute: Cannot get image rotation

DxOCorrectionEngine - Error | InternalError: In Block LightingV3Estimation@node_12937[0].Execute
In Block DxO::Node::Execute [ identifier=LightingV3Estimation m_internalMode=Preview m_scale=0 m_inputROI.StringRepr()=[ (x=0, y=0, w=480, h=640) ] outputs.nodeOutputData->value=outputImage=computeOutputInfoOk=true outputImageValidROI=[ ] outputROIs=validateOutputPolicy=FullOutputData outputROI=[ (x=0, y=0, w=480, h=640) ] invalidROI=[ (x=0, y=0, w=480, h=640) ] validROI=[ ] priority=10 ] [ ctx=000002ACE31C9D30 ]
Correction failed on the Execute stage

9

Could well be related to size as I always use soft and don’t recall it befor

10

Tried with some 640 x 480 jpeg generated by PL - no problem, the size is not an issue.
Maybe some required metadata is missing – only DxO can say.

11

That’s what I’m thinking as well.

Mark

12

Put in a bug report

13

Yes, I could reproduce the error message when invoking “Spot Weighted”,
but without any crashing, and went back to “Uniform”.

Then using the Hue mask selection (top right corner)

Screen Shot 10-14-24 at 04.15 PM.PNG
Screen Shot 10-14-24 at 04.15 PM.PNG2165×1167 486 KB

and optimizing the selection a little I could remove the yellow colorcast

Screen Shot 10-14-24 at 04.16 PM.PNG
Screen Shot 10-14-24 at 04.16 PM.PNG2164×1165 488 KB

VC1 → IMG_0628.jpg.dop (18,6 KB)

and export

IMG_0628_1
IMG_0628_1480×640 92 KB

14

Thanks sorted it in Affinity.

1 Like
15

You begin to lose the will to live dealing with support. They haven’t bothered to test the bug but sent an almost incoherent message re new version. What “Our Team had made some update and right now, we will need to have it uninstalled and back in your device.” is meaning I think I worked out install the new version.

Any way bug still there and I did point out testing the bug would have been quicker than sending the massage. As others have pointed out higher levels of support are good, at times, just until you get there its mind blowing.

16

Oh well nothing new. Support still not actually tested the image but ask again if I still have the problem Pointed out it was, as they asked, last tested by me on 8.1. Its a good thing this isn’t a bad bug but I can see the idea is get me tom give up and them not have to do anything. No wonder for many customers support has a rather poor reputation,

17

Support really has no intention of doing anything with this. With many much bigger bugs some years outstanding (e.g. on occasion jumping images when using the browser accepted as a bug and promised having a fix back in V2) I can see why from there angle. Now they have switched to wanting a copy of the RAW image after being told it’s a small jpeg many times. Their approach is PL is sold as supporting and editing jpgs but we don’t do anything about bugs when using jpgs. Rather than honestly saying this they try to get you to give up.

18

No wonder many give up with support. No matter how many times they are told the bug relates to using a jpg they keep saying they cant open it and send the raw. I can open the uploaded jpg.