"Show tonal map" kills ART 1.5 in Windows 10

[Using ART 1.5 in Windows 10]

While editing any file type (.ORF, .RW2, .CR2, .JPG, etc.) in Editor mode, attempting to activate “Show tonal map” in Exposure > Tone Equalizer shuts down ART down immediately without warning or error message. Either of two scenarios produce this result:

(1) First, open Tone Equalizer and activate it (by clicking on the small circle next to “Tone Equalizer”). Next, click on the box next to “Show tonal map”. ART closes.

(2) First, open Tone Equalizer but do NOT activate it. Next, click on the box next to “Show tonal map”. ART stays open and colored circles appear next to the sliders. Finally, activate Tone Equalizer. ART closes.

Is this behavior expected?

Of course not :slight_smile:
But I cannot easily reproduce here either… at least on Linux. I’ll try on windows. What version are you using? The “official” installer or did you compile ART yourself?
Thanks!

I just tried, and can’t reproduce…

I can reproduce it with AboutThisBuild.txt (571 Bytes)

I will try to see if it crashes also with gdb attached to get some logs.
Very interesting is that if I am starting ART from the MSYS2 console (so attached to a console) it will not crash. But if I am starting it from the shortcut icon (not attached to any terminal) it does crash.

I managed to reproduce it using a debug build and created agriggio / ART / issues / #126 - "Show tonal map" kills ART 1.5 (Version: 1.5-12-gf528be7b9) in Windows 10 — Bitbucket

All the needed information should be there …

Thanks for the report. Can I ask a couple more questions?

  1. Does this happen with all images?
  2. Does this happen with the “official” installer?
  3. What version of LCMS are you using?

Thanks!

Here the answers:

Thanks. I suspect some issue with the latest version of lcms2. Maybe I’m misusing the library and the newest version doesn’t tolerate that. I’ll take a closer look.

A.

1 Like

You’re welcome!

I think you are right about the lcms2. At least in the logs there is nothing that looks totally wrong. If you need more details, let me know.

(Apologies for the delay in replying to your question.) I did not compile ART but instead installed it using the downloaded file ART_1.5_Win64.exe. Actually, when first encountering the unexpected behavior described above, I uninstalled the first copy of ART, downloaded the installation file again, and reinstalled ART. No change in behavior was seen.

FWIW, I am using Windows 10 Home Edition, version 2004.

thanks, this is definitely useful

A.

FYI, should be fixed in master now