Skip to main content
Adobe Photoshop Family

2 Messages

 • 

250 Points

Mon, Aug 4, 2014 4:38 PM

Solved

Lightroom: Issue with Map module in OS X 10.10 (Yosemite)

On OS X 10.10 (Yosemite), the map in Lightroom's Map module is very slow to load. It takes several minutes before the first part of the map appears, and some parts don't load at all, saying instead "Sorry, we have no imagery here", even though the part in question is on Google Maps. When zooming in or out, it's the same, it takes very long to update.

Responses

47 Messages

 • 

550 Points

6 years ago

Mark, Dave and Martin i bow to your knowledge thank you saves me a lot of hassle looking, have any of you considered re installing Mavericks i admit it really annoys me 2 of the largest companies and they can't save this seems crazy

Cheers

Allan

159 Messages

 • 

4.2K Points

6 years ago

Just to add to the above, the longer you leave the Maps module 'loading' the bigger these numbers get! After 2 minutes they are 10Mb and 48Mb respectively. The screen shot above was after just a few seconds of Maps 'loading'.

1 Message

 • 

80 Points

6 years ago

It seems that there are some issues with the google maps statistics. Simply open the console.app and filter for lightroom. It shouldn't be to hard to fix...

33 Messages

 • 

374 Points

Ding. Well spotted. Now all they have to do is fix it.....

47 Messages

 • 

550 Points

no idea what that all means but i for one thank you for applying light

47 Messages

 • 

550 Points

6 years ago

Just a thought guys

my thread is
https://forums.adobe.com/message/6862...

If you each add as following maybe adobe will look and i have asked in that thread that look here again least it may get a look from Adobe

Champion

 • 

5.2K Messages

 • 

93.4K Points

6 years ago

I think it would help if everyone experiencing this problem would report back the following:

- Open the "Console" app and see if you are getting the same "HTML Trace" messages that Jan Freuer observed two posts above.

- Open Activity Monitor and report on the Data Received/Sec and Data Sent/Sec. Several people have observed that data sent (uploads) is unusually large.

47 Messages

 • 

550 Points

I am happy to do this but don't know how what is a console app please

Champion

 • 

5.2K Messages

 • 

93.4K Points

Click on the Launchpad in the dock (the rocketship icon), type "Console", hit enter. Do this right as LR is trying to display the map. If you're getting the "HTML Trace" messages that Jan Freuer saw, you'll see them displayed.

33 Messages

 • 

374 Points

6 years ago

I get exactly the same error:

A parse error on map.googleapis.com

Champion

 • 

5.2K Messages

 • 

93.4K Points

Do you also have unusually large data sent/sec, similar to what Dave Roberts reported above?

On your second machine, which you reported didn't have the problem, are the Console messages present, and does it have unusually large data sent/sec?

Narrowing this down makes it somewhat more likely Adobe will address it sooner. (And I agree that users shouldn't have to do that, but that's the reality of today's consumer software.)

33 Messages

 • 

374 Points

yes - I checked it with nettop, mentioned it in the thread above. I have very very slow tile fetch and failure, the same console traces, and lots and lots of data being sent out.

My issues are identical.

33 Messages

 • 

374 Points

I haven't checked the second machine. maps on it work, but there are only about 6 images on it, and none are geotagged.

33 Messages

 • 

374 Points

...further, if I pre-fetch the tiles, by clicking on "report a map error", bottom right, I can get it to "work", after a fashion.

47 Messages

 • 

550 Points

6 years ago



Not sure tried load what i think from console

Champion

 • 

5.2K Messages

 • 

93.4K Points

Yes, your console log also shows "HTML Trace" errors from Lightroom, with names that indicate it's related to the maps.

47 Messages

 • 

550 Points

Thank you John glad that it helps the cause good old google had no idea what console was

33 Messages

 • 

374 Points

6 years ago

This is quite bizarre. We have a major company, an acknowledged bug for 3 months and complete, utter, stony silence from the company.

I have to say I am struggling to see what Adobe's game plan is here. It certainly isn't going to keep them in pole position. Real shame, because Lightroom is a very nice piece of software. But 5/6 of Lightroom for 12 weeks isn't. Especially when a bunch of users appear to have located the problem.

It's the silence which is annoying.

159 Messages

 • 

4.2K Points

6 years ago

I totally agree Mark, Adobe's silence on this is both bizarre and unacceptable.

What are they so scared of? They should have broad enough shoulders to at least acknowledge the issue. Very disappointing from a company that actually charges a lot for their software which I am happy to pay when it works!!

47 Messages

 • 

550 Points

6 years ago

I have just left Trustpilot review of LR and asked that trust pilot forward this onto adobe maybe they will read that
https://www.trustpilot.co.uk/review/w...

33 Messages

 • 

374 Points

6 years ago

Dear Mr Adobe,

I don't think you're reading this. And I don't think you're going to fix this quickly, despite the fact that you have known about it for three months.

As a last-ditch attempt to get going again, I'm going to install LR in my parallels Windows 8.1 partition and try it there. If it barfs about licensing issues, I think I'll probably go off my trolley. I assume this is ok with you?

But, to be honest, I'd much rather Lightroom actually worked on the Mac.

33 Messages

 • 

374 Points

Now this *is* bizarre.

I've initiated the download (of LR) in Windows 8.1 in parallels. To kill time, I flipped back to the running lightroom in the native Mac....and the maps download =:-O

If I pause the windows download after a few seconds the maps stop. If I restart the windows download, after a few seconds maps starts working again.

Utterly bizarre.

159 Messages

 • 

4.2K Points

6 years ago

Mark

How totally bizarre! I will experiment later......

33 Messages

 • 

374 Points

Pretty conclusive. I have just had an hour of perfect maps, and managed to geotag loads. The download finished in Windows 8.1/Parallels and bingo, back to "Sorry we have no imagery here".

If the machine isn't actively downloading somewhere, then LR won't fetch. Actiev download anywhere (including other VMs in //) then it works.

Utterly bizarre. What on earth is going on?

6 Messages

 • 

110 Points

6 years ago

I recently upgraded my desktop and laptop to OSX 10.10 and now find the Maps section of Lightroom 5.6 crippled. On both of my machines the maps either fail to load, load partially (missing tiles), or load very slowly (~15 minutes).

I rely on the Maps section and geotagging for my work. Please attend to this issue, which I understand has been known for three months now.

Help!

159 Messages

 • 

4.2K Points

6 years ago

Mark

I tried your 'solution' and sadly it did not work for me, however I use VMWare not Parallels, maybe that is the difference?

The only thing that consistently works for me is plugging my iPad that has 4G (15mbs download and 5mbs upload) and using it as a usb hotspot, a Map Module works absolutely fine then!

117 Messages

 • 

2.9K Points

6 years ago

We are still investigating this, but no solid leads yet as to what changed in 10.10 to upset this, sorry. I'd appreciate hearing what video cards are in the systems that are running into this, because we're finding it inconsistent across hardware but haven't found the pattern yet.

11 Messages

 • 

276 Points

Hi Julie,

the video card in my mid-2011 iMac is an AMD Radeon HD 6970M 2048 MB

My internet connection is DSL with 16MBit down, 1MBit up.

7 Messages

 • 

182 Points

Julie - Thanks at least for responding / acknowledging. I am on a NVIDIA GeForce GTX 680MX 2048 MB

2 Messages

 • 

70 Points

NVIDIA GeForce GT 650M 512 MB
The Mapmodule worked fine untill Yosemite. My bandwith surely doesn't cause the problem.
And now please fix it or give back my money!