iTunes 11.4: Console messages: Failed to create replacement string

What functional problem do you have, if any? Log messages are not a problem in themselves.

Please sign out of the iTunes Store and sign back in. Test.

Same with me : after a general freeze (had to restart with power button on) the message "Failed to create replacement string" appeared multiple times on the console after console.

Partially the cause of the crash perhaps?

Never happened with 10.9.4 ou previous iTunes versions.

Best

I have these messages also. Hundreds of entries when iTunes is open. Signed out/sign in, same problem. Computer restart, same problem. Stops when iTunes is closed. Looking to see if anyone has found a solution yet.

MBA mid 2012, latest Mavericks, have not updated devices to iOS8 yet.

Here is a snippet of bug message in between the "Failed to create string" spam messages -

9/20/14 5:15:05.232 PM iTunes[348]: Failed to create replacement string

9/20/14 5:15:39.153 PM com.apple.WebKit.Plugin.64[361]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.

9/20/14 5:15:39.153 PM com.apple.WebKit.Plugin.64[361]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

9/20/14 5:16:30.553 PM com.apple.WebKit.Plugin.64[361]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.

9/20/14 5:19:17.156 PM iTunes[348]: BUG in libdispatch client: kevent[EVFILT_WRITE] delete: "No such file or directory" - 0x2

9/20/14 5:19:17.286 PM iTunes[348]: Failed to create replacement string

the same here. Impossible to sync , stuck in the last phase.

Iphone 4S 8.0, MacBook Pro Retina 15 i7 2,6, 10.9.5 and iTunes 11.4

Log messages are a certainly problem in themselves in some cases. They make debugging nearly impossible when spewed out at that rate and with no hint at all at what the problem might be.

And I really would love to fix the issue with itunes but don't know where...

Got the same error messages in console, dozens at a time. What's causing this?

This message has been mentioned in several threads linked to the latest version of iTunes being unable to sync iDevices. Seems like the sync function aborts after a while, and goes into a loop, leading to memory leak, and the console reflects that loop.

Finally I followed that thread stuck on waiting for changes to be applied

Remove most of the buggy applications or musics. And it did it.

Adding little by little with some backups between syncing.

Sorry, but while Manu276had actually the problem the thread you mentioned tries to fix (obviously successful for most people),

my iTunes syncs perfectly well, only it spams my console and my log files. Even on a brand new installed Mavericks with brand new itunes, albeit after importing some music.

And there ist no fix available for that, not even a workaround it seems.

Pretty disappointing - why would one need debugging messages without anyone being able to interpret them and take action.

II agree with you unidojhf. They coded something wrong in one of the updates. Not sure if it is ios 8 or the iTunes update, or combo of both. but something didn't go right and we are seeing console spammed with that message. They need to figure it out and fix it. I sent an email to the feedback link, but who knows if/when someone will read it.

In the the meantime, what are you guys doing? have you restored to before the iTunes update, or are you just sitting tight as is?

Iam a weekend Mac user, during the week only use my iOS devices. As far as iTunes syncing, everything works fine on everything and is synced. So as long as I don't use iTunes on the Mac today, I don't have to deal with the console messages until next weekend. Hope they send some sort of update with a fix this week.

Same here. I update before my last sync and now it will not recognize my 5c.