This is the last time I will post here. I have started a new thread on the issuses that I believe this QTKitserver is a merely a symptom.
But seriously, as IT "professional" you do not know that "launchd" can spawn over 20 subprocesses? Or it can "spawn" the "sh" prcess which can call/spawn the "sed" process, multiple times, and these can eat more than 60% of the CPU for minutes before the system decides to give up and kill them. Processes spawned by "launchd" are the most likey culprit to the SWOD. The "launchd" manages processes, processes for the system and users. It is Macs preferred way to launch deamons (ie, spawned processes). It is processes spawned (launched) by "launched" that are where the issue is. Which processes, Apple initiated or third-party is unknown to me, but there should be code within OS X to trap and gracefully degrade poor code by error trapping.
Please stay within this thread where you are comfortable.
Please stay on topic, you have completely hijacked this thread with your rubbish. Please start your own thread!!!!
I'm sorry, but you're not making any sense, with your spelling, its impossible to tell what you're trying to say.
You mismash words together that do not make sense. I'm not sure what university you studied at but it obviously wasn't the same one I went to.
launchd and launchservicesd do you mean? Where are you getting your assumptions from? Please post data, not rubbish.
The only time I ever have CPU usage over 60% is when using video converters, or flash on safari. I'm not a gamer, but that will spike CPU.
You must have some serious rubbish installed on your Mac if lauchd services are giving you these spikes in CPU usage.
Again, please provide data, without it, you are just talking utter rubbish. So please, post some data. You hardware, OS, software that causes the issue.
Sigh, just make your own thread.
thank you... for you support... I have posted most of what I've posted here on the forum for OS X developers forum and have not had any misunderstanding. We're actually engaging in promising discussions. It seems that you are king of this this thread and are directing where you are comfortable. Please continue, I seek answers, not "who's king of the hill".
Why not post a thread here? I'm sure we'd love to see your data. Seriously, post a new thread explaining your issues.
When you come to a thread and give no data, no details, no information whatsoever, but use statements like,
"APPLE - we're calling you out --- what is the basis of this issue? Here's a thread that persisted for years, you can google it yourself, yet there's no answer. Provide us with an expalination and fix !!!!!!!"
"Where's Apple on this issue... nonexist on this thread. Does that tell you something???"
"My Windows machine, now hwastes less time than my MacBook Pro... Apple, get it together before it's too late."
"Not very funny, agreed... this problem has presisted since 2008 and specifically focused on Safari since 2010. Do your homework. The point of the post was to say that Quicktime and Safari interactions areridddled with bugs. Where on this entire forum thread is there any APPLE authority telling us ***. is going on. You can keep on praying that it gets fixed. It's not Maverick, it's crapping programming.Until APPLE corrects it, their reputation is falling quickly."
"Check this site for some history and possible solutions, assuming apple doesn't pull this post:"
Again, feel free to post system reports, data, specs or any other information with your accusations. Perhaps then someone might take you seriously.
Post the link to the OSX developer forum too. Thanks.
<Edited By Host>
@Andrew J :
I have participated in the thread for some months now in a constructive matter to no avail. I have also provided input as much as my average skills allowed. And, to be frank: I'm also starting to become a little "unhappy" as there are quite some people really trying to solve the issue but nothing happening on the Apple-side (evidenced by the fact that 10.9.1 did not solve the issue)
While I'm writing that, another process stopped working. Since you like reports, here we go:
/Library/QuickTime/Flip4Mac WMV Import.component/Contents/MacOS/Flip4Mac WMV Import
<Edited by Host>
Details are important, and if someone cannot be understood, how can anyone help if statements are unclear, filled with spelling errors and uses nonsensical jargon?
Did you read any of his previous posts? Perhaps you should first, to gain some context. It helps nobody if all one can do is make nonsensical, unhelpful, disparaging remarks, and after making many (reasonable) requests for some sort of data to support his crazy claims, he never provided anything, not once. Which leads me to think this person did not come here for answers, just to vent his bile towards Apple, for whatever reason. But hey, go right ahead if you want these forums to be hijacked by trolls like him. People like me will just leave, if thats what you want. His rant was totally misleading to those who ARE looking for answers and nothing but unhelpful and wastes peoples time.
In reference to the original problem, it looks like the issue stems from an redundant background process that causes a loop creating the QTkitserver non response issue. You have Flip4Mac installed, so perhaps uninstalling that, and Perian, if you have it, may help. The issue doesn't create any problems for the CPU or memory, so it can be ignored until the issue has been addressed by Apple.
<Edited By Host>
Thank you for confirming all my points, Andrew!
"…there are quite some people really trying to solve the issue but nothing happening on the Apple-side (evidenced by the fact that 10.9.1 did not solve the issue)"
I acknolwedged and appreciated the efforts by people like you but I'm missing Apple's participation.
Also, it seems that some of your rant has been removed by the host, too. "That says a lot, don't you think?"
Lots of time wasted, indeed.
In reference to the original point: I have a MacMini running almost without any 3rd party extensions (use it for iMovie, Aperture). Same issues here. No Flip4Mac installed. Perian I don't know. Certainly not installed.
The issue is that sometimes those crashed processes have an impact on the cooling of my MBP. The fan goes havoc or the machine gets hot without the fan. I found that phenomenon in other forums as well. Killing the crashed processes gets the fan to normal. So, there is some connection here.
Mac MacBook Pro has the 3rd motherboard now. I know that this is a know issue (mainly thermal issue). That's why I'm so nervous about cooling.
Apple will never openly discuss any issues like bugs or hardware, unless it is an systemic issue, across the board and reported widely.
If you haven't already made a report about your issues through the Apple feedback pages, I would suggest that you do.
Early generation Mac Minis had cooling issues as the heat syncs were located right next to the heat sensors, I know, I had one myself. A little bit of re-engineering on my part fixed the problem. They also had wifi antenna problems because of its location.
As for MacBooks, I have always advised my clients to never ever place them on flat hard surfaces whilst doing CPU intensive work, like movie editing, photoshoping, encoding, etc. One client burnt out his motherboard on his MacBook Air within 2 years of purchase as all he did was video encoding. When he showed me where he kept his MacBook, it was obvious why. Motherboards will cook, no matter what computer you use, be they Mac or PC, if simple precautions are not taken, it is inevitable. This is why Apple don't call their laptops, laptops. Propping up the back at least an inch, is enough to avoid cooking your motherboard. It is physics, not a design flaw.
I've not had an issue with my 4 year old MacBook pro, except for swapping out bigger HD, and a 12 year old iMac that hasn't skipped a beat. I believe if you treat them right, they will repay the favour.
On other forums, regarding this issue, software engineers believe that it a latency issue of redundant processes left behind when Mavericks was installed. It points to the fact that Apple have shifted their A/V component support from Quicktime to CoreMedia. There's something going on there, but nobody has been able to pinpoint it. This is why I suggested removing any plugin components that rely on quicktime to handle A/V support. Perian certainly did, as did the previous version of Flip4Mac.
If you use iMovie then check your user library for older plugins from older version of iMovie, and or third party ad-ons. Until then, we just have to wait it out for a fix, but I assure you, there's plenty trying to pinpoint this issue.
Thanks for your feedback.
I know Apple for 30+ years now and can confirm your statement. However, hope dies last.
I have reported it back and so did many of my friends.
No cooling issue on my latest MacMini (as of yet)...
MacBook sits on 4 little silikon bumpers which leaves about 1cm between the bottom and the surface. Thus, that should be OK for air refresh. I know for a fact that the motherboards had a series of faulty production. They missed the heat-transmission paste between the cooling and the Video processor which cooked that one. I'll see how long this MB lasts.
Well, my Mac+ still works (albeit only for some HyperTalk-fun). Bought it in 1986. I have another MacMini (first Intel-Generation) which is my media center and runs 24/7 since 3-4 years without a glitch.
Let me put it like this: Using Apple has always been a bit more expensive for a simple reason: Ease of use and quality.
The existence of a forum like this should alert Apple, since in the past, this has been the privilege of Windows XP-users.
The problem seems to stem from the user Library, so if you did a clean install and reinstalled from a backup, all the redundant processes return. Others have mention the QTkitserver not responding issue does not appear when logged in as root user. I haven't tested if it presents under a new user account.
If it isn't causing you any CPU issues, then ignore it. It has been recognised by Apple engineers, and we can hope a fix is coming down the pipeline.
In my case it isn't a Safari issue - I've been noticing my QTkitserver freezes since updating to Mavericks. Turns out in my case it was that I was using the new iPhoto/iCloud features of allowing family to upload their photos/videos to my shared photo streams. Prior to Mavericks this wasn't an allowed feature... in fact sharing videos is new to iPhoto 9.5.1
Today I removed all videos posted to my photo streams - since QT is a video-based process - and the QTkitserver has stopped freezing up.
My issue was that every time I opened iPhoto it would hang once it started the process of attempting to update iCloud photostreams. IPhoto itself would beachball out, and Activity Monitor would show both iPhoto and QTkitserver as red.
The same held true with Aperture, which makes sense since it shares the exact same library as iPhoto.
I know this isn't a Safari-based issue in my case, but perhaps it can help to lead you on your way to discovering the cause of why it also happens in Safari as well as other applications.
I believe this has happened because Apple have moved away from using QuickTime as their backend A/V component support and gone to using CoreMedia instead. Somewhere along the way, certain background processes continue to look to QTkitserver to perform a process, that it is no longer supported under Mavericks, hence the non responsive action from QTkitserver.
I originally thought that Perian & Flip4Mac, and other components that used QuickTime support, were the issue, because they all work across the system to provide support for unsupported media within applications like Safari, iPhoto and Aperture, as well as system services like quicklook, and use QuickTime to support their plugins. This is as close as I've been able to come to pinpointing the issue, but I'm certain it stems from a process that has been made redundant by Mavericks using CoreMedia to support A/V media in the backend.
My only suggestion is to remove things like Perian, Flip4Mac and other plugins that use A/V component support from the system and applications like iPhoto, iMovie and other third party media editing apps, for the time being, until updates are pushed out to fix things.
In my case, I had gone through a clean re-install of Mavericks and no "back to my Mac" or anything for fear of bring back across some problem I may have introduced. I have no 3rd party installs, just iWork and iLife suites.
So in my case, simply deleting movies from my iPhoto and/or streams did the trick. For others, your suggestions are a bit extreme but certainly sound... it would turn what should be an expensive but amazing computer into a low-class paperweight. If you were to suggest Boot Camp partitions, install Windows 8 and run off that... I wouldn't be surprised at this point. At least it would work!