I installed a 2TB SSD in my 2012 Quad i7 Mac Mini and upgraded from 8 to 16GB of ram. I went ahead and installed the Mojave upgrade (from El Capitan) and since I got rid of the dual RAID config, I created a Win10 BootCamp partition (used my old unused Win8.1 Pro key I bought on sale for $68, which will register Win10 Pro). Everything seems to be hunky dory, overall. Both OSes boot in 20-25 seconds and the machine feels almost like new again (maybe better in terms of disc access).
BUT, the one problem I've been having consistently since upgrading is that when I start iTunes now, it goes to 100% CPU usage (11% total) when it starts and stays there for ??? Hours? If I leave it there and go to bed the next morning it'll be down to normal CPU usage for iTunes, but if I quit it and restart it, it's right back to 100% for hours and hours again.... WTF!?!? What is it doing??? I haven't watched a movie or played a music file or done a darn thing with it. If it's updating some files or something, it should have been done when I left it overnight, etc., but here I'm sitting 10+ minutes after starting it and it's STILL at 100% CPU.
This is absolutely unacceptable behavior. And the weird thing is that I'm pretty certain it did NOT have that problem in El Capitan. I would have noticed like I did here. So why would it change just going to Mojave? Did Mojave have a newer version that was not available for El Capitan? I forget what version it was at, but checking now it's at v12.9.5.5.
I've mostly moved to using KODI 18.3 Leia over SMB3 for all local media (I've got three AppleTV units in use for streaming), but I still get a hiccup with music once in awhile that doesn't happen with iTunes (and it never happens if I use Windows 10 to serve the music to KODI so something is amiss in macOS there as well) to my AppleTV units so I liked to leave it running, but not if it's going to use that much CPU power doing nothing.
Is anyone NOT having this issue with iTunes in Mojave? Could something be messed up after the upgrade? Media plays just fine from Mojave and even as old as my Mac is, I can't "feel" anything slow in iTunes itself, but the Activity Monitor doesn't lie.
I've been watching the Disk and Network use and it's not using either. So whatever it's doing at 100% CPU is just within iTunes itself and isn't using any disk or network activity.... weird.
BUT, the one problem I've been having consistently since upgrading is that when I start iTunes now, it goes to 100% CPU usage (11% total) when it starts and stays there for ??? Hours? If I leave it there and go to bed the next morning it'll be down to normal CPU usage for iTunes, but if I quit it and restart it, it's right back to 100% for hours and hours again.... WTF!?!? What is it doing??? I haven't watched a movie or played a music file or done a darn thing with it. If it's updating some files or something, it should have been done when I left it overnight, etc., but here I'm sitting 10+ minutes after starting it and it's STILL at 100% CPU.
This is absolutely unacceptable behavior. And the weird thing is that I'm pretty certain it did NOT have that problem in El Capitan. I would have noticed like I did here. So why would it change just going to Mojave? Did Mojave have a newer version that was not available for El Capitan? I forget what version it was at, but checking now it's at v12.9.5.5.
I've mostly moved to using KODI 18.3 Leia over SMB3 for all local media (I've got three AppleTV units in use for streaming), but I still get a hiccup with music once in awhile that doesn't happen with iTunes (and it never happens if I use Windows 10 to serve the music to KODI so something is amiss in macOS there as well) to my AppleTV units so I liked to leave it running, but not if it's going to use that much CPU power doing nothing.
Is anyone NOT having this issue with iTunes in Mojave? Could something be messed up after the upgrade? Media plays just fine from Mojave and even as old as my Mac is, I can't "feel" anything slow in iTunes itself, but the Activity Monitor doesn't lie.
I've been watching the Disk and Network use and it's not using either. So whatever it's doing at 100% CPU is just within iTunes itself and isn't using any disk or network activity.... weird.
