com.apple.geod process is not responding

i Wold be interested to know, because I wont assume, if your location services are working. Maps, weather widget if you use it, etc. thanks

The location services seem to work, since I see the weather widget finding my location as does Maps etc. Still the com.apple.geod process is hanging. I force quit it here and then, but only the red error message goes away, the now active process still cannot be force quit. I agree, Apple does know about this item, but since it has few effects on Yosemite, they don’t care much about it. I don’t see we have any chance to fix this „problem“ - we can only hope that Apple accidentally may fix it.

Anyone try the 10.10.2 update for a fix?

I applied the latest 10.10.2 update and still the same issues. No location services working at all and geod not responding. I have Apple support so going to try them next but from other forums I have read they can't fix it either. Looks like a wipe of the drive and back to Mavericks!

That's exactly what I did. I'm back on Mavericks 10.9.5, and everything is much better other than the way it looks. I can't believe it's taking this long for Apple to fix a long known problem. No thanks for iDevice integration. I will never use an iPhone. I really like my rMBP13 with Mavericks 10.9.5.

I also went back to Mavericks although I have Yosemite installed on an external drive that I use to test the system. The only issue that was fixed for me with 10.10.2 was now TM works correctly but other issues are carried over.

Ok, I got the 10.10.2 update installed yesterday and have been testing it since then. As of now, here are my findings:

1. Apparently the App Store will also trigger com.apple.geod. But ONLY when you actually download something. Starting the app itself and browsing around will leave it be. But as soon as a download starts, App Store calls up the command. My best guess is that Apple is querying GPS data from iOS devices to find out the real location of the Macintosh to find the most physically closest server to allow for the fastest download. In other words, it's entirely for QOS. A very, VERY smart idea indeed. Both in terms of customer experience, but also for location services. You can't always trust a computer's location based upon IP Address. Google always thinks that I live 10 miles away because that's where my ISP's (Comcast's) STC is located. And at work Google thinks I'm 1,400 miles away elsewhere. I also wonder if this might be used for marketing? Either by Apple, or 3rd party websites where you grant it permission to use your location and send you notifications. But that's a whole other discussion...
2. com.apple.geod has been screwing up Time Machine in a BIG way. When the computer would wake up past the last scheduled backup, Time Machine would of course initialize, but would absolutely lock up on "xxxMB of xxxMB backed up" when you checked on the progress. And it would just sit there. Now Time Machine is bad enough on it's own with slowing down OS X (especially noticeable on a Core2Duo using a USB 2.0 external drive), but this would drag the system down to an unspeakable level of slowness. ESPECIALLY if you woke the Mac up and had to immediately switch user accounts. It wasn't quite locked up, but it almost felt like it. But as soon as you terminated the com.apple.geod process, it would immediately speed back up and complete as usual. This was a replicated on 10.10.1 even after checking for errors on the Macintosh HDD as well as repairing Permissiosn, ACLs, and defragmenting the drive using Drive Genius 3. So it certainly wasn't an issue with the HDD.
3. Having said all of that, performance now is almost night and day having upgraded to 10.10.2! That is NOT to say that the com.apple.geod process locking up has been resolved. It absolutely has NOT! But it's impact is greatly improved. I will have a bit of a hump that Time Machine has to get over, but then after about 20 seconds or so it continues with the backup no problem. Even with com.apple.geod sitting in the background locked up, performance has greatly increased. I can now open up apps with only a minimal delay during the Time Machine backup, and then they run just fine as normal when TM is complete. It's only been a short period, but I will keep monitoring it.
4. There is still no way to tell just yet if the memory leakage issue with com.apple.geod has been resolved. That is the worst part. If Saved Application State keeps loading it's previous memory allocations back into place each time it starts, and this memory leak issue is not resolved, that's a problem. As I said before, over the course of months after upgrading to 10.10 I found that the process had consumed 2.83GB of my total 4GB of memory. Needless to say that's not good at all. So far that appears to be the final problem that Apple may not have resolved, but only time will tell. If it's not resolved, doing a weekly to biweekly purge wouldn't be so bad. But it's still not something I'm wanting to do at all, and should not have to.

Interesting observations. For me I never saw any functional changes with TM backups or my Mac running slow or locking up. Just saw the red com.apple.geod not responding in the Activity monitor.

I am running a Vintage Core2Duo CPU w/4GB of RAM. So it's not absolutely not as powerful as the modern i5 & especially i7 CPUs Apple has been selling for a while. Plus I'm also using USB 2.0 for the external HDD for Time Machine. Plans are to swap out the HDD for a bigger SSD, and I might also get the FireWire 800 adaptor for the external drive to help speed things up further to keep this machine going for a year or two more. I'd be shocked if the next version of OS X will be compatible, but Apple might just wait until units are fully obsolete until they drop support for OS Upgrades.

Anyhow, there has been a HUGE breakthrough!

Cons:

So as it turns out, com.apple.geod still has that pesky memory leak issue. I can watch it creep up. It does release some small amount of memory back if you close out a dependent app, but it still creeps right back on up.

Pros:

1. Apple may very well have been paying attention here. As I've found OS X is now purging com.apple.geod when the user account logs out! It might be a fluke and I'll continue watching it, but so far it's been happening. Previously if one account had triggered the process it would remain running while the user logged out, and right on until the next user logged in. Not now. Now when I log in the process is entirely gone.
2. When OS X stops com.apple.geod it now also purges it's memory! So when I log into another account, not only is the process gone, but it starts up using only 480K instead of where it previously was! This is wonderful!

With this new development this issue is all but resolved for the most part! The only problem would be if you were to never ever logout or reboot your machine. I've no idea if this issue is present under OS X Server, but if it is, this could very well be a major issue if admins never bother to restart their servers. Especially since so many ignore updates.

In the end, com.apple.geod still locks up, but it no longer affects other processes and applications in OS X. This is a marked improvement. I'll continue to monitor and we'll see where it goes from here.

I have a Mac mIni and I auto shut down every night so it clears out the process when I restart the next morning just like you have indicated. I guess if you only set to sleep in the same user then it would remain. Knowing Apple it could take some time (if ever) that this gets addressed. By then the next OS will be released.

II've been seeing this issue for a few weeks. As of the last 24 hours or so, com.apple.geod kicks off a cascade problem. First that process hangs, then Safari hangs. In the process of using feedback assistant, other processes begin "not responding". This is getting bad... To the point of being unusable.

com.apple.geod was behaving the way you describe as the new behavior for me - not persisting from one account to another, that is - prior to this upgrade, so I'm not sure that this is attributable to the upgrade.

The only thing that has worked for me is switching from Safari to Chrome. com.apple.geod still rears its ugly head from time to time, but rarely, and almost always it's directly attributable to another Apple program - App Store, iTunes or Calendar. Even though every imaginable pref for location services is turned off, it still comes back once in a while. But the constant drain and hang-ups have stopped ever since dropping Safari.

And I'm finding Chrome to be a vastly superior browser, anyway. Much faster and more stable.

com.apple.geod was haunting me the way you describe, constantly, and sucking so much memory that the machine slowed to a crawl every few minutes.

The answer - though not a total fix, it comes back once in a while, though rarely - was to switch to Chrome and never again open Safari. The problem has almost entirely vanished, though com.aple.geod is still called up by other Apple programs, such as App Store, iTunes, Calendar. But for the most part, this ended a huge headache.

Apple has it's head up its ***. I was on the phone with Support over this issue for FIVE WEEKS. They had no clue what was going on, or so they said. It's hard to believe. I personally know two other people with this issue, so it's hard to imagine it not happening anywhere but on this forum and to my friends, but that's the new Apple for ya.

Anyway, keep Activity Monitor open, force quit c.a.g, download and open Chrome, use the Chrome assistant to bring over your bookmarks, and you'll be up and running in ten minutes.

Safari itself does not trigger the com.apple.geod process per se. It's when you constantly allow websites to send you notification messages within Safari that the process gets triggered. Take a look here for an example:

These notifications can utilize Location Services, and can start up when you launch Safari to check for updates for the Notification center starting the process along the way. Notice that I've blocked all but one notification service, in this case the one for eBay. I know that this one does not use Location Services, so I allow it. So whenever I start up Safari, I never have a problem with com.apple.geod launching.

So if you have a problem with Safari triggering this process, it's because you allowed 3rd party sites access. Stop allowing everyone to send you notifications and you shouldn't have any more trouble. And in the future, if you ever get a popup notification on a site like the one below, just click "Don't Allow".

As a side note, I have found that Safari runs much faster than Chrome when it comes to normal web browsing, and especially Adobe Flash animations. In particular Farmville and other Facebook games. I honestly only have two legit reasons to use Chrome:

1. Webpage Compatibility for certain websites. In particular Oracle/PeopleSoft.
2. Shopping. It's well know that some sites will see Safari as the browser and raise the price on items. So I use Chrome for online purchases on websites that I don't fully trust for pricing. Travel and Reservation sites are the perfect example.

I also installed an 480GB PNY SSD tonight to replace my aging 7½ year-old HDD. A marked improvement all across the board, and most of my problems have now been resolved. So again, aging hardware also plays a major part in this problem too. Let's still hope that Apple takes the appropriate steps to resolve things with perhaps a self-terminating timer for the process too. But otherwise, unless you've got a major malfunction that is affecting the entire OS like I had, just don't worry if your only problem is a process that isn't responding.

I see you are still finding some interesting info. Funny but I find Chrome (at latest 64bit level) to run faster than Safari. May have to do with what extensions and plugins are installed.