#8951 (Bug) Display calibration hangs on “Using CAM Jab for clipping”
+1 1
New
Component: DisplayCAL
Created by proslambanomenos
Last modified
I’m using DisplayCAL 3.3.4.1 with an X-Rite i1 Display 2 on a MacBook Pro running Sierra.
After ~15 minutes and DisplayCAL has appears to have finished using the i1 Display 2 colorimeter to take shots of many color swatches, the “Create profile from measurement data…” action begins and, when it reaches the “Using CAM Jab for clipping” job, it hangs forever. This has happened 2 out of 2 times I’ve tried. The first time it hung at 77%. The second time it hung at 44%.
Attaching logs and a screenshot.
Aborting (image/png | 2017-09-21 19:40:18)
myMac (image/png | 2017-09-25 18:32:21)
adjust (text/plain | 2017-09-21 19:36:53)
DisplayCAL-fault (text/plain | 2017-09-21 19:36:53)
DisplayCAL.1 (text/plain | 2017-09-21 19:36:53)
DisplayCAL (text/plain | 2017-09-21 19:36:53)
interact (text/plain | 2017-09-21 19:36:53)
wexpect (text/plain | 2017-09-21 19:36:53)
UsingCamJabForClipping (image/png | 2017-09-21 19:39:06)
adding screenshot
Also, canceling/aborting the operation never succeeds. It hangs forever too… attaching screenshot.
How much RAM does the machine have?
16 GB (attaching screenshot of system info)
That should be more than enough RAM. Does the UI stay responsive (i.e. animations keep running)?
yes, the ui animation doesn’t “freeze”–things _appear_ to be working, but the progress bar/percentage number never advance after waiting a long time, etc.
In that case, I would recommend letting it run overnight to see if it finishes at all.
I ran into this today and think I found the problem, and a fix. I am using a late 2013 Macbook Pro, with an i7. I noticed an error in the DisplayCAL-fault.log file, to the nature of “illegal instruction”. Searching around, it appears that the newer versions of DisplayCAL come with a bundled version of Python. That particular error seems to be due to an instruction that’s incompatible with the machines CPU. My guess is that the Python binary isn’t fully compatible with all the Mac hardware.
The way I solved this was to copy the python executable that was the system default into the DisplayCAL bundle. Specifically:
From a terminal:
Confirm the python version with: “python –version”. It should be 2.7 (I’m on Sierra)
From a terminal, locate python 2.* using the command: “which python”. For me, and most users, it should be located at /usr/bin/python
Open the DisplayCAL bundle (application in Finder) by right-clicking the application and selecting “Show Package Contents”. This will open a Finder window that exposes the application bundle. It’s just a folder on the file system. Navigate into /Contents/MacOS/. You should see some files, including the bundled Python executable. Leave this window open.
You now need to rename this, and copy over the python binary from /usr/bin. You can do this from the terminal, or from Finder. I just used the “Go To Folder.. (Shift-Command-G)” from finder, and entered “/usr/bin”. Locate the python binary, and drag it into the /DisplayCAL/Contents/MacOS folder. (The cursor should turn into a green plus, indicating a copy)
Once you do this, DisplayCAL should use the version of Python that is 100% compatible with your Mac. By doing this, I was able to perform calibration, characterization, and have a profile created with no hanging at this final stage.
Good luck!
– Sean
This has been always the case for the standalone version.
Hmm. That is a bit surprising since it uses the official python.org 32-bit/PPC Python (available from additional downloads) for Mac OS 10.5 compatibility (although I’m likely to drop PPC support by switching to the 32-bit/64-bit Python in the not too distant future, bumping the minimum compatible version of OS X that DisplayCAL will be able to run under to 10.6).
Please try the 3.3.6 Beta which is now targeting Intel only. Does the segfault persist?