iBooks runs "storeaccountd" process that runs CPU at 100% and drain battery

Unfortunately need to confirm.

It is quite sad as I have bought new mac few days ago only because of battery - I need to work during my long trips. And ibooks is something I need to do my job.

You can only imagine how dissapointed I was when I had 4h trip by train and my mac died before I've reached destination point. And the only opened apps were ibooks and xcode. Cmon.

I took am experiencing this problem with Yosemite and iBooks - storeacountd spikes and kills the battery in my 2013 Air. It also only happens when there is no internet - it's like it is trying to sync the progress of my book to my iPhone even though it is not connected. It may not affect someone who does not have another device loaded with iBooks attached to their iCloud account, however this is only a hypothesis.

Upgraded to Yosemite 10.10.1 there is no change in behaviour. 😟

same problem os Yosemite 10.10.1 and further after a certain amount of annotations it becomes unresponsive to further annotation.

That is possible, I have reported fixing of this bug after 10.10.1 but I have no synchronising of my Ibooks with iCloud and devices.

People reporting future bug appearance may check their sync settings.

Even with Sync off the issue is there. Don't know when will they fix it. IBooks was one of the biggest reason of buying the mac. Apple please fix this ASAP. I don't think it should take so much longer time.

Second it. The problem is, that stupid service just bangs connections like a machinegun. I have a firewall enabled, and that thing goes online without asking nicely.

Apple devs, the correct way you code any online service:

1. on the first run you should state clearly that service will run periodically, tell user what it does, and give option to "manual override"

2. keep track of failed connections

3. apply threshold, after which exit for n-minutes before retry (and retry wait should progress)

4. repeat until connected

Thats it. That simple. Happy coding!

Having the same problem. Here is a temporary fix:

- in Activity monitor, determine the PID of the storeaccountd process

- open Terminal.app

- type "kill -STOP <PID>" (e.g. if your storeaccountd's process Id is 1184, then type "kill -STOP 1184")

This will effectively pause that application (killing it outright doesn't work because it will restart the same way). To resume it, you can type:

- "kill -CONT <PID>"

This fix works in that the CPU drops back down to zero. Obviously, whatever service storeaccountd is providing will be unavailable while it is paused.

Thank God. Update 10.10.2 fixed this. Updated yesterday night.

Open terminal > (type) "pkill -f storeaccountd" (without quotes) and put this command on loop. I know its not rigid solution but it worked for me .. may be it could help you Thanks! 🙂