Skip to main content
Known Participant
February 2, 2023
Answered

Firefox and Lightroom Classic incompatability

  • February 2, 2023
  • 11 replies
  • 2413 views

Hi, If I open Lightroom Classic simultaneously with Firefox, my computer grinds to a halt. I am not the only one. One of my fellow writers at Fstoppers is experiencing the same issue.

When raising this with Mozilla support, the reply came back:

"Sounds like both Firefox and LightRoom is using the same memory locations an could be slowing down the process. This would be something you need to ask Adobe support since it seems to occur when Firefox and LightRoom process are both used."

I'm using Windows 10, with an AMD A10 processor and 32 GB RAM.

This topic has been closed for replies.
Correct answer GoldingD

In the meantime, an inquiry:

 

  • Where do you keep your CAMERA RAW CACHE? /preferences/performance/Camera RAW CACHE/. What hard drive.
  • If C drive, do you have another drive?
  • How large do you allow it to get? What limit?

 

11 replies

GoldingD
GoldingDCorrect answer
Legend
February 6, 2023

In the meantime, an inquiry:

 

  • Where do you keep your CAMERA RAW CACHE? /preferences/performance/Camera RAW CACHE/. What hard drive.
  • If C drive, do you have another drive?
  • How large do you allow it to get? What limit?

 

ivortogAuthor
Known Participant
February 7, 2023

It's on the C Drive in the default location. The dive is a 2 TB SSD, less than half full.

I had increased the cache size to 20 GB, but now changed it to 25 GB. 

Yay, I think that may have done the trick. Thank you so much.

Community Expert
February 6, 2023

It apears you are running an antivirus software (Norton). Try disabling it as a test as well as any other AV software. The system interrupts being at 100% is a sign of something else blocking access to the computer's resources which will lock it up. AV is a typical culprit. Also try disabling the grammerly plugin. There are lots of reports of it slowing down firefox enormously and even locking it up. So disable all plugins/extensions in Firefox and disable your AV software.  

ivortogAuthor
Known Participant
February 6, 2023

Yes, I have already tried disabling the FF extensions to no avail. I'll give the AV a try. Thanks

GoldingD
Legend
February 4, 2023

If you open the Windows Event Viewer, what issues show up? 

ivortogAuthor
Known Participant
February 6, 2023

Nothing significant at the times when I have both open at once. There is a Warning that tells me that " The resource 'C:\ProgramData\FLEXnet\Connect\11\ISDM.exe' does not exist." appears occasionally.

GoldingD
Legend
February 6, 2023
quote

Nothing significant at the times when I have both open at once. There is a Warning that tells me that " The resource 'C:\ProgramData\FLEXnet\Connect\11\ISDM.exe' does not exist." appears occasionally.


By @ivortog

So:

C:\ProgramData\FLEXnet\Connect\11\ISDM.exe

That has nothing to do with LrC, nothing to do with Firefox, little or nothing to do with Windows. 

 

ISDM, appears to be a InstallShield Update Service Download Manager. And in your case, for a program from Flexnet.

 

Flexnet appears to be a provider of various apps for IT asset management, software licensing management, etc. 

 

Is this computer the property of your employer? is it managed by an IT department? Do they know what this is?

 

The apparent failure of this app might be fouling your computer up. Any odd thing occuring on a computer should be fixed before thinking another program is not working, buggy.

GoldingD
Legend
February 4, 2023

Do you keep either your catalog or your photos on your network, or the cloud?

ivortogAuthor
Known Participant
February 6, 2023

The catalog is stored on the same 2TB SSD as my OS. Then there are 3 x 1TB SATA SSDs that hold my pictures. Each is backed to the cloud, and are fully synchronised. Thank you.

Community Expert
February 4, 2023

The fact that it only happens in develop makes me think this might be a GPU issue. Does it still happen if you disable the GPU in Lightroom? What kind of GPU do you have? Are the drivers fully up to date? I don't use windows but there is probably a way to show the GPU resources in task manager. See if they max out. Lightroom Classic is VERY GPU intensive.

ivortogAuthor
Known Participant
February 6, 2023

Hi thanks. Yes, My drivers are up to date (I use Driver Easy) and I had tried turning the GPU off.  I have an Nvidia GForce GTX 1050 Ti. which is 4 GB. I am using 2 x 1920 x 1080 displays, not 4K, so it should be well within scope. The issue is only with Lightroom Classic and none of the other programs I use.

 

ivortogAuthor
Known Participant
February 4, 2023

Hi again all,
I have been doing some digging following the helpful  suggestions here. (Thanks all)
1. Disabling the plugins doesn't make any difference.
2. The issue occurs when I am in the Develop module, not in the Library. It can happen at any point while using the develop module, but definitely every time I try to apply a local adjustment. Switching back to the Library, which takes about ten minutes, does not correct the issue.
3. The entire computer grinds to a near halt.

You can see how slow the computer gets by the following screenshots where the snipping tool was able to get a screenshot of itself. Lightroom was not responding at this point and the selected raw image (.orf from an OM-1) would not display.


4. Sometimes System Interrupts and sometimes System processes show 100%.
5. Force stopping Firefox does not stop the issue, but force stopping Lightroom by ending the process does.

The issue doesn't exist with other browsers and Firefox does not exhibit this behaviour when using ON1 Photo Raw, DxO PhotoLab 6, Capture One,  or Lightroom (new version, not classic.)

Thank you.

Ivor

Ian Lyons
Community Expert
Community Expert
February 4, 2023

Try disabling the GPU. If doing so fixes the issue, then check that you have the most up to date driver. 

Conrad_C
Community Expert
Community Expert
February 2, 2023
quote

When raising this with Mozilla support, the reply came back:
"Sounds like both Firefox and LightRoom is using the same memory locations…”

By @ivortog

 

Technically, two applications literally using “the same memory locations” should be impossible on a modern operating system, and if it did happen, what should happen next is not slowdown but a crash of one or both applications, and possibly the operating system too. That’s not happening, it’s only a slowdown…so that explanation is unlikely. Maybe they meant that using those two applications together uses up too much memory, but again that is unlikely on a computer with 32GB RAM.

 

If there is a major slowdown, open Windows Task Manager and see if a specific process is using an unusually high amount of CPU, and if so, what is the name of that process?

ivortogAuthor
Known Participant
February 4, 2023

Thank you. Please see my reply below.

Rikk Flohr_Photography
Community Manager
February 2, 2023

I've tested on Win 10 and see no difference in Classic speed behavior, prior to or after launching Firefox. 

Rikk Flohr: Adobe Photography Org
ivortogAuthor
Known Participant
February 4, 2023

I guess computers are so complex with such a variety of different hardware and software options, that what happens for one doesn't necessarily work for another.

Keith Reeder
Participating Frequently
February 6, 2023

Thank you for that reply. It was more about the customer service experience that I was considering writing about. As I pay a subscription to Adobe, I do expect them to provide a product that is compatible with my system, and give support if it isn't. From a customer point of view, being told by representatives of Adobe, (paid or volunteer) "I don't have that problem" is not entirely helpful.

I don't find it strange that others aren't having the same problem. When I look at these sorts of issues, there are inevitably people who do and don't get them. For example, I reviewed ON1 Photo Raw a while back, and someone replied that they had difficulties with it. I didn't, but I referred them to where they could get help. Looking through this forum, there are plenty of other reorts of people having rare and unusal issues.


quote

being told by representatives of Adobe, (paid or volunteer) "I don't have that problem" is not entirely helpful.

 

You should find it very helpful. It clearly suggests that the problem is with your local environment (which - as an aside - you can't seriously expect Adobe to take responsibility for) rather than anything inherent in LightRoom.

 

Most "rare and unusual" problems Lr users have, pretty much invariably track back to something about their machine: from what you've written so far there's no convincing reason at all to believe that you're an exception to that.

 

Specifically: you'd have to evidence that a LightRoom/Firefox contention that happens to you and not to others, is still inherently a LightRoom problem. You're going to struggle to do that.

TheDigitalDog
Inspiring
February 2, 2023

On a Mac, no conflict (I have both running all the time). 

Best to contact Mozilla.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
dj_paige
Legend
February 2, 2023

No problems here with Firefox and LrC. Windows 11 (but previously on Windows 10 and Windows 7 no problem either).

 

Have you looked into the plug-ins used by Lightroom Classic and the add-ons used by Firefox to see if one of those might be a problem?

ivortogAuthor
Known Participant
February 4, 2023

I'm giving those a go. Thanks.

Ian Lyons
Community Expert
Community Expert
February 2, 2023

It's always the other guy whose doing it wrong 😉

 

If Mozilla think there's a memory conflict with Lightroom Classic, then it's for them to chase up with Adobe, not their customers.

 

 

 

ivortogAuthor
Known Participant
February 4, 2023

I agree to a certain extent, but it is equally Adobe's responsibility, especially as none of the other photography DAM or development apps have the same issues with Firefox.

 

Keith Reeder
Participating Frequently
February 4, 2023

By the same token, LightRoom doesn't have this issue with other browsers - and it's easier to be flexible about the browser you use...

 

(In fact it doesn't happen with Firefox, here on my Win 10 Home machine.)