iTunes 12.2.1 hangs during playback on Yosemite 10.10.4

Question

Level 1

10 points

iTunes 12.2.1 hangs during playback on Yosemite 10.10.4

This strange behavior happens everytime since I updated iTunes to the latest version. During playback, usually after 4 o 5 songs, iTunes hangs with a miserable and perpetual spinning beachball. I have to force quit and restart the sucker.

I tried to test it with brand new libraries (both a smaller and a larger one), deleting preferences, deleting plugins folder, reinstalling it, and so on: still the same behavior.

Since I'm out of DIY options, I'm asking if anyone is struggling with this problem too and how could you eventually solve it.

Thanks!

Specs:

iTunes v12.2.1.16

Yosemite 10.10.4

MBP 13" (mid 2012), 2,9 i7, 16GB RAM

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10.4), null

Posted on Jul 28, 2015 4:41 AM

Reply

Answer 1

Best reply

Linc Davis

Level 10

209,547 points

Jul 28, 2015 6:30 AM in response to thebranka

When you see a beachball cursor, note the exact time: hour, minute, second.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

The title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Reply

Answer 2

thebranka Author

Level 1

10 points

Jul 28, 2015 6:58 AM in response to Linc Davis

Thank you. Here it is:

28/07/15 15:52:58,000 kernel[0]: process iTunes[1391] thread 305638 caught burning CPU! It used more than 50% CPU (Actual recent usage: 72%) over 180 seconds. thread lifetime cpu usage 102.520740 seconds, (98.414617 user, 4.106123 system) ledger info: balance: 90000213351 credit: 102505713280 debit: 12505499929 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 124004132827

28/07/15 15:52:59,002 com.apple.xpc.launchd[1]: (com.apple.ReportCrash[1898]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash

28/07/15 15:52:59,004 ReportCrash[1898]: Invoking spindump for pid=1391 thread=305638 percent_cpu=72 duration=125 because of excessive cpu utilization

28/07/15 15:53:00,405 spindump[361]: Saved cpu_resource.diag report for iTunes version 12.2.1 (12.2.1.16) to /Library/Logs/DiagnosticReports/iTunes_2015-07-28-155300_BrankaBook-Pro.cpu_res ource.diag

Here's the report:

Date/Time: 2015-07-28 15:54:06 +0200

OS Version: 10.10.4 (Build 14E46)

Architecture: x86_64

Report Version: 21

Command: iTunes

Path: /Applications/iTunes.app/Contents/MacOS/iTunes

Version: 12.2.1 (12.2.1.16)

Build Version: 2

Project Name: iTunes

Source Version: 1200012002001016

PID: 1391

Event: timeout-lite

Duration: 9.90s (process was unresponsive for 2 seconds before sampling)

Steps: 100 (100ms sampling interval)

Hardware model: MacBookPro9,2

Active cpus: 4

Fan speed: 1994 rpm

Heaviest stack for the main thread of the target process:

100 ??? (iTunes + 9028) [0x108926344]

100 ??? (iTunes + 8615238) [0x10915b546]

100 -[NSApplication run] + 594 (AppKit + 551667) [0x7fff8bdafaf3]

100 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 (AppKit + 593496) [0x7fff8bdb9e58]

100 _DPSNextEvent + 978 (AppKit + 596139) [0x7fff8bdba8ab]

100 _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 205099) [0x7fff911d612b]

100 ReceiveNextEventCommon + 179 (HIToolbox + 205294) [0x7fff911d61ee]

100 RunCurrentEventLoopInMode + 235 (HIToolbox + 206191) [0x7fff911d656f]

100 CFRunLoopRunSpecific + 296 (CoreFoundation + 465880) [0x7fff8ba01bd8]

100 __CFRunLoopRun + 872 (CoreFoundation + 467336) [0x7fff8ba02188]

100 __CFRunLoopDoObservers + 368 (CoreFoundation + 524416) [0x7fff8ba10080]

100 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 (CoreFoundation + 524583) [0x7fff8ba10127]

100 __35-[NSWindow _postInvalidCursorRects]_block_invoke3353 + 46 (AppKit + 8217105) [0x7fff8c4ff211]

100 _handleInvalidCursorRectsNote + 1077 (AppKit + 1388210) [0x7fff8be7beb2]

100 -[NSView(NSInternal) _updateTrackingAreas] + 1857 (AppKit + 1390489) [0x7fff8be7c799]

100 -[NSView(NSInternal) _updateTrackingAreas] + 898 (AppKit + 1389530) [0x7fff8be7c3da]

100 -[NSView(NSInternal) _uninstallRemovedTrackingAreas] + 391 (AppKit + 443573) [0x7fff8bd954b5]

100 -[NSSet objectsWithOptions:passingTest:] + 234 (CoreFoundation + 681882) [0x7fff8ba3679a]

100 __NSSetEnumerate + 766 (CoreFoundation + 682814) [0x7fff8ba36b3e]

100 __40-[NSSet objectsWithOptions:passingTest:]_block_invoke + 53 (CoreFoundation + 682981) [0x7fff8ba36be5]

53 objc_msgSend + 26 (libobjc.A.dylib + 4314) [0x7fff88e750da] (running)

Binary Images:

0x108924000 - 0x10a29afff com.apple.iTunes 12.2.1 (12.2.1.16) <085F4192-29CC-3CB0-9B42-BFB39F405A01> /Applications/iTunes.app/Contents/MacOS/iTunes

0x7fff88e74000 - 0x7fff8906efff libobjc.A.dylib (647) <759E155D-BC42-3D4E-869B-6F57D477177C> /usr/lib/libobjc.A.dylib

0x7fff8b990000 - 0x7fff8bd28fff com.apple.CoreFoundation 6.9 (1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

0x7fff8bd29000 - 0x7fff8c8aafff com.apple.AppKit 6.9 (1348.17) <E485D56D-3E72-34B7-99BB-BFDEE2D07BF5> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit

0x7fff911a4000 - 0x7fff914a9fff com.apple.HIToolbox 2.1.1 (758.7) <083019EB-7F58-36F1-BF7F-9E746F692E5C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox

Any ideas?

Reply

Answer 3

Linc Davis

Level 10

209,547 points

Jul 28, 2015 7:07 AM in response to thebranka

Please read this whole message before doing anything.

This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of this test is to determine whether the problem is localized to your user account. Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest by creating an iTunes library and importing a few tracks. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault in OS X 10.7 or later, then you can’t enable the Guest account. The "Guest User" login created by "Find My Mac" is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Reply

Answer 4

thebranka Author

Level 1

10 points

Jul 28, 2015 8:21 AM in response to Linc Davis

Thank you.

I created a new standard account and logged in (ignoring the Apple ID login part). Opened iTunes on the new account, imported several hundred mp3s and so far it's working fine. It's been more than 30 minutes now.

I tried again my main account iTunes and exactly 6 songs in it hanged again.

Reply

Answer 5

Linc Davis

Level 10

209,547 points

Jul 28, 2015 8:42 AM in response to thebranka

Please sign out of the iTunes Store in your own user account and see whether there's any change.

Reply

Answer 6

thebranka Author

Level 1

10 points

Jul 28, 2015 9:55 AM in response to Linc Davis

Turned off genius, signed out, restarted iTunes and now it doesn't hang anymore... What should I do? I'm confused: Is my Apple ID messing with the app?

Reply

Answer 7

Linc Davis

Level 10

209,547 points

Jul 28, 2015 12:17 PM in response to thebranka

At the top level of the iTunes folder, there should be a file named "iTunes Library Genius.itdb". Move that file to the Trash. Quit and relaunch iTunes, then enable Genius and test again.

If there's no improvement, repeat with the file named "iTunes Library Extras.itdb".

Reply

Answer 8

thebranka Author

Level 1

10 points

Jul 28, 2015 12:23 PM in response to Linc Davis

Exactly what I did after disabling it and logging out. I think the problem is finally gone. Thank you thank you thank you for helping me solve this!

Reply

Answer 9

Aug 25, 2015 6:53 AM in response to thebranka

I noticed iTunes would use over 100% CPU usage only when switching to the mini player. In preferences, I turned on "keep mini player on top" and I no longer have the problem with excess CPU usage. Im assuming that small change created a new preference file and thats what did the trick.

Reply