Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Who's currently at 10.12.6 with your mac pro?
- Thread starter pat500000
- Start date
- Sort by reaction score
Did more tests. Result shows that the Finder UI hang (and subsequently discovered iSight hang) ONLY happen when all CPU cores under high stress.
Since my cMP was encoding video almost 24/7 after upgrade to HS. That's why I get the hang. If I pause the process, Finder is perfectly fine, and iSight also never hang.
Since I only pause the process, but not stop of finish it. Therefore, the RAM usage clearly is not the reason of those hang. Couldn't quite understand why high CPU stress will cause the Finder UI hang (or iSight hang). It's clearly not "waiting for CPU resource", because when beach ball happen, even I pause the video encoding (CPU back to idle), Finder / iSight still hang.
May be HS make Finder (or some software) can either get the CPU resource now or never. If at that moment, CPU recourse is not available, then the UI hangs (until relaunch).
I also tested the "renice" command in terminal, make the video encoding priority to 20 doesn't help anything.
Since my cMP was encoding video almost 24/7 after upgrade to HS. That's why I get the hang. If I pause the process, Finder is perfectly fine, and iSight also never hang.
Since I only pause the process, but not stop of finish it. Therefore, the RAM usage clearly is not the reason of those hang. Couldn't quite understand why high CPU stress will cause the Finder UI hang (or iSight hang). It's clearly not "waiting for CPU resource", because when beach ball happen, even I pause the video encoding (CPU back to idle), Finder / iSight still hang.
May be HS make Finder (or some software) can either get the CPU resource now or never. If at that moment, CPU recourse is not available, then the UI hangs (until relaunch).
I also tested the "renice" command in terminal, make the video encoding priority to 20 doesn't help anything.
Last edited:
This is not good for me then since i do video editing stuff. What's your alternative?
Most of the time I use FFMpeg to encode video, that's easy to limit the core usage by the "-threads" parameter. I usually only give it 8 threads to use out of 12 available. I prefer to keep 4 free threads which makes my computer always responsive.
However, when I use DVDFab to convert 4K BD into 4K 3D SBS MP4, the software automatically use all threads available regardless my setting. This is the only time that I may have Finder hang.
(It's not DVDFab causing the Finder freeze. I can reproduce the issue by running FFMpeg without limiting the cores usage)
Since DVDFab can easily be paused. So, my work around is simple. Keep it running until I hit the Finder issue. Pause DVDFab, relaunch Finder, and use my cMP to do my work. Then continue DVDFab when I finish using the computer.
I have no rush to convert the BD anyway. It's basically the "background process" for me. Pause it for a while doesn't really matter.
I only use FCPX for about 30min, no issue so far. I bet FCPX is not heavy enough to reproduce the issue. But if you have video encoding in the background, and FCPX in the front, then it may be another story.
I expect they can, And already report to them with all the sysdiagnosis info, but no reply from them yet.