Under normal load, 1.6.0rc1 seems stable as far as I can tell so far.
But when I switched to Sierra, I also finally converted my iPhoto archive, which resides on a zfs dataset, to Apple Photos. And there seems to be some problem.
The conversion worked, I can start and use Photos, but when things gets a bit more intense on my zfs photo dataset, then sooner or later I end up with kernel task deadlocked at 100% CPU in an apparent busy loop.
I am not able yet to give you an exact sequence to reproduce the error. But say you are working in Photos (which means it reads a lot from disk) while it is still scanning in the background the images for faces (photolibraryd and photosanalysisd also churning away on the same dataset) and you have the photo library still selected in a Finder window (which means Finder also scans that directory to determine the size of the library), then there is a good chance getting to this stage. There is then also a good chance that Photos or Finder become unresponsive so that I needed to kill them. The 100% kernel CPU remains however even after killing Photos and Finder. I can then also only reboot with a hard reset on the power button, while a soft reboot will hang
At this very moment, my kernel is on 100% after I quit Photos successfully and the photolibraryd+photosanalysisd kicked in, and with no problems in Finder at all. The system is still responsive and I can access the ZFS datasets. But the kernel task skims through on something around >= 100%. Memory usage seems maxed out: according to Activity Monitor, 15.36 GB of 16GB are used, kernel task at 12.39 GB memory usage. Yes, my photo library is definitely larger than 16 GB
I get lots of entries in system.log of the following form:
default 11:43:15.993628 +1100 kernel SPL: arc_reclaim_thread: post-reap -207515648 post-evict 0 adjusted 0 pre-adjust -207515648 to-free 214855680 pressure 0
Any ideas?
