Skip to main content
Adobe Photoshop Family

4 Messages

 • 

140 Points

Thu, May 17, 2018 8:26 AM

Lightroom Classic: dynamiclinkmediaserver hogs processor even when no Adobe apps running

Please get dynamiclinkmediaserver under control. It hogs huge amounts of processor even when no Adobe apps are running. All I can do is to keep removing the dynamiclinkmediaserver folder from Application Support. But then it gets regenerated when I run Lightroom Classic CC

Responses

Adobe Administrator

 • 

7.9K Messages

 • 

114.5K Points

2 years ago

Kevan, 

What is your Operating System Version?

Can you give me figures on how much processor it is using - or even better a screen capture?

Adobe Photography Products
Quality Engineer: Customer Advocacy

4 Messages

 • 

140 Points

2 years ago

Rikk

Mac OS 10.13.4
c.93% CPU — see attached screen grab

I have been using Lightroom Classic CC for several hours, and dynamiclinkmediaserver was not running. As soon as I quit Lightroom it starts to run! How can you explain that?

4 Messages

 • 

140 Points

2 years ago

I have just received the most absurd email from Adobe:

"You contacted us on 5/17/2018 1:26 PM. We have resolved your Performance issue and are closing case number ADB-2175542-K6W5."

a) Nobody has resolved my issue
b) It is SO DIFFICULT to actually find the case in question
c) When I did finally discover how to find it, there was no way of commenting or reopening it.

Needless to say, I would still like feedback about my issue.

Thanks

Adobe Administrator

 • 

7.9K Messages

 • 

114.5K Points

2 years ago

Thanks for the screenshot. I have forwarded to the Dev team for comment. Stand by. 

Adobe Photography Products
Quality Engineer: Customer Advocacy

1 Message

 • 

80 Points

Hi - is there any fix for this? I've had this problem through the last several versions of the OS and of Lightroom. Running OSx10.14.1, Lightroom Classic 8.0, Build 1193777. See screenshot of Activity monitor with no Adobe apps open for hours
Thanks!

4 Messages

 • 

140 Points

2 years ago

Thanks Rikk

10 Messages

 • 

188 Points

My screen has since updated, but my CPU% for dynamiclinkmediaserver was... wait for it... 423%. It's a 4-core machine. How is this even possible? 

1 Message

 • 

60 Points

2 years ago

I have the exact same problem, no adobe apps running (LR CC, LR CC C) still medialinkserver is 100%  of my cpu and the fan is running like crazy. What should I turn off? And how do I (or you) fix this? I have a macbook pro touch bar 2016, and the latest version of both LR apps. 

1 Message

 • 

80 Points

2 years ago

And so, Rikk Flohr? 8 months, and no response? I have the same problem and I'm close to throwing the entire Adobe ensemble of resource hogs off my machine.

12 Messages

 • 

200 Points

a year ago

Same problem here.  After running an Adobe app I have to force quit the dynamiclinkmediaserver manually to keep it from consuming 100% of a CPU.

1 Message

 • 

60 Points

a year ago

Same issue here, ate up 447 hours on my imac. Pretty close to ditching adobe software as well. WTH, a year goes by and this is still an issue? 

1 Message

 • 

60 Points

a year ago

Same.  Just moved back to Lightroom Classic after a couple of years away.  Sad to see this.

MacOS 10.14.6

Standing by, Rikk Flohr

10 Messages

 • 

346 Points

a year ago

I have the same problem.  Everytime I quite Lightroom Classic, dynamiclinkmediaserver runs up to 99% and stays there until I kill it.  I am running macOS 10.14.6 on a late 2012 MacBookPro with LR Classic 8.4.1.  It has done this for at least the last year.

2 Messages

 • 

70 Points

7 months ago

I am having the same issue. Any solutions yet? 

6 Messages

 • 

130 Points

6 months ago

same happening on windows 10 latest build. Im tired of lightroom. i cannot do simple tasks as import pictures/videos (sync folder) because dynamiclinkmediaserver grows up with no limit and lightroom never get back the control.

1 Message

 • 

64 Points

5 months ago

I'm having the same problem running Lightroom classic. Good thing I'm running the trial version, now I know I don't want to spend money on software that has had this problem for years without a fix.