Lightroom Classic: The picture panel goes black and the program crashes

  • 6
  • Problem
  • Updated 5 days ago
  • (Edited)
LR classic CC crashes
Photo of Adri

Adri

  • 2 Posts
  • 0 Reply Likes

Posted 7 months ago

  • 6
Photo of Venkatesh Penjuri

Venkatesh Penjuri, Official Rep

  • 40 Posts
  • 8 Reply Likes
Hi Adri,

Are you on Windows? Could you share us your system info here?

Help->System info->Save as and share the text file.

Thanks
Photo of Adri

Adri

  • 2 Posts
  • 0 Reply Likes
I am on windows 10, at this moment I'm not at my computer and cannot reply now, I'll send the info later today. Thanks.
Photo of Venkatesh Penjuri

Venkatesh Penjuri, Official Rep

  • 38 Posts
  • 5 Reply Likes
Is your graphic drivers updated? If not, please update your graphic drivers and let me if this helps.
Photo of Chandan Kumar

Chandan Kumar, Official Rep

  • 28 Posts
  • 9 Reply Likes
Also could you try turning GPU off to identify if the issue is with GPU or the driver?

Thanks,
Chandan
Photo of gar nix

gar nix

  • 4 Posts
  • 0 Reply Likes
crashes in develop mode every time
Photo of Venkatesh Penjuri

Venkatesh Penjuri, Official Rep

  • 37 Posts
  • 5 Reply Likes
If the crash is on windows, updating graphic drivers should help. Please try it out after updating the drivers. Also, after Lr crashes, you will get a crash report please submit that.

Thanks
Photo of gar nix

gar nix

  • 4 Posts
  • 0 Reply Likes
driver is up to date (see post below)
crash report was sent
Photo of gar nix

gar nix

  • 4 Posts
  • 0 Reply Likes
turned GPU off and had no crash; turning it on again LR crashes immediately.
(windows 10, latest graphic card driver)
do better not update!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3807 Posts
  • 1259 Reply Likes
Which graphics card and driver gar nix?
Photo of gar nix

gar nix

  • 4 Posts
  • 0 Reply Likes
NVIDIA GeForce GT 630M
23.21.13.8792
Photo of Adri van Oudenaarden

Adri van Oudenaarden

  • 1 Post
  • 0 Reply Likes
I switched off the GPU, LR is working now

NVIDIA GeForce 750M
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
same here, Windows 7, Radeon RX 470:

switching to Develop module with GPU support on blacks out my image:



interesting:
when restarting Lightroom the first switch to develop module works correctly, switching back to the library module and the again to develop another picture leads to this black image phenomenon
(Edited)
Photo of Allan Hamilton

Allan Hamilton

  • 9 Posts
  • 1 Reply Like
I have this same problem. I did notice that the switch to open GL sped up the response to slider movement but back and forth between Library and Develop the black screen problem still exists.
I also note a seeming disconnect between the filmstrip selected photo and the selected photo identified in the grid....
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3831 Posts
  • 1269 Reply Likes
Some people are finding option 2 on this page helps:  https://helpx.adobe.com/lightroom/kb/crash-gpu-directx-enabled.html
(Edited)
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
Nope, does not solve the problem on my system
Photo of Allan Hamilton

Allan Hamilton

  • 9 Posts
  • 1 Reply Like
Speeds up sliders but still a problem.
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
Some additional information:
The bug (black image) does not occur when starting LR, switching the ONCE to the development module and then moving between images (using the filmstrip).
It only occurs when switching back to the library module selecting another image and switching to the development module with this new image!!
As I wrote the bug occurs also when Develop.PreferOpenGL = true.
It occurs also when using the newest video driver.
It didn't occur in LR CC 7.12.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Windows update don't always pull and install the latest GPU driver, especially for older hardware or legacy OSes. Try going to vendors' download site to install the latest drivers:

Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
I downloaded the driver via the Radeon tool.
Why did LR 7.12 work with my video card and driver and activated GPU support and the new version fails after switching twice to the development module?
Is there a logging option to help Adobe identify the exact error scenario on my system?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Lr Classic CC switch to Windows native GPU API DirectX for improved ongoing support. Apparently it did not work out in your case. After you've updated the GPU driver and still experiencing problem. I suggest follow tip #2 https://helpx.adobe.com/lightroom/kb/crash-gpu-directx-enabled.html to see if you can get it to work reliably. If it still not working, try tip#3. 
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
As I wrote above #2 PreferOpenGL=true doesn’t work on my system. The error stays the same even when I enable to prefer OpenGL.
Tip#3 (disabling GPU support) is of course a minimal option.
Photo of Ron meiburg

Ron meiburg

  • 2 Posts
  • 4 Reply Likes
My Lr Classic CC does not crash, but I have precisely the same issue with the black image. The effect is created by opening the Develop Module on any image. Then switching off the 'Use Graphics Processor' (it was on at start)  and then switching it back on. The image will then go black instantly.
The second screen still shows the image.
Photo of Arnold Bartel

Arnold Bartel

  • 163 Posts
  • 37 Reply Likes
Which configuration does your System have? Operating System, video adapter, screen Resolution?
Photo of Ron meiburg

Ron meiburg

  • 2 Posts
  • 4 Reply Likes
Some extracts from Lr's System Info. 

Lightroom Classic version: 7.0.1 [ 1142117 ]
License: Creative Cloud
Operating system: Windows 7
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2,8 GHz
Built-in memory: 8182,0 MB

Displays: 1) 1920x1200, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
OpenGL: AMD Radeon HD 5700 Series

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 3.3.13417 Core Profile Context 15.301.1901.0
Renderer: AMD Radeon HD 5700 Series
LanguageVersion: 4.40
Total Video Memory: 1011 MB


I downloaded the 16.2.1 Radeon drivers, Crimson edition. These are the latest although over a year old. They did not fix this issue.

I guess I failed to make clear in my initial response that there was not only a very simple way to reproduce the phenomenon that you raise, but that the way it occurs suggests the bug is in Lr and not in any of the other components of the system.
We have a common goal here.

Trust this helps
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes

Another detail for you Adobe guys to solve the problem:

When you start LR CCC with GPU support enabled and with a picture in development mode you can move between the images using the filmstrip without any Problem AS LONG AS YOU STAY IN DEVELOPMENT MODE. When you switch to library mode everything works fine. But switching back to development mode you have to select a picture which was already opened in development mode before (e.g. those which was selected when you switched to library mode).

Otherwise (when you Switch to development mode having selected a "new" Picture) this black Screen issue occurs.

So it seems to be a bug in a part of your code which is executed to load the picture into memory when switching from library to development mode.

Photo of Valerio Albo

Valerio Albo

  • 2 Posts
  • 0 Reply Likes
Me too ... I tried all, update Windows, update any kind of drivers, but in the library module I don't see the preview, it seems that the preview don't refresh only gray/black window, but switching to develop module, and also on the second screen, the image appears ... I think it is a LR's error.


What a joke ... I hope that Adobe will solve this problem asap
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
Photo of Valerio Albo

Valerio Albo

  • 2 Posts
  • 0 Reply Likes
Thank you Simon, it works!
Photo of Michael Zunke

Michael Zunke

  • 1 Post
  • 0 Reply Likes
It also worked for mr. Though I have a variation of the symptom. If my LR Classic loads too many pictures in Library mode at startup it gets stuck on rendering these. Sometimes I can still do some unrelated interation untill it finally hangs, sometimes it is hanging non responsive right away.
Setting Config.lua-Flags:
AgView.disableDirect2D = true
Fixed the issue. Switching on/off the use of the GPU made no difference.
Maybe it helps on debugging or others to fix their issue...
Mike
Photo of John Price

John Price

  • 3 Posts
  • 1 Reply Like
This reply was created from a merged topic originally titled Lightroom Classic CC problem.

Since switching to Classic CC I am getting a black screen when move from Library to Develop. The R/A and Y/Y options display properly, and when I close LR in the develop mode, the photo shows correctly when I re-open the program.
Library Mode:


Switch to Develop mode (the histogram responds to changes):


Switch to Y/Y in develop mode:


I am using Windows 7 Professional 64.
I have un-installed and re-installed with re-set preferences.

Please Help

Brian Price
Photo of John Price

John Price

  • 3 Posts
  • 1 Reply Like
Thanks, switching off the GPU solved the problem.

Brian
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
unfortunately this bug is still not fixed in the current LR CC classic 7.1 version.

It's really strange that the picture is displayed properly in devekop mode when switching to Y/Y options but in normal display mode we only get a black screen.

Please fix this bug to reenable the GPU enable option!
Photo of wzhou41

wzhou41

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom Classic CC: Photo is completely black in Develop screen with GPU accele....

Enabling GPU acceleration in Lightroom Classic CC causes the entire photo in be black in the develop module.

Closing and restarting Lightroom will fix the issue, but it returns if I go into the LIbrary module, and then select a different photo to develop. 

Disabling GPU acceleration is the only way to definitively fix the issue. I am working with 46 MP files on a 2560 x 1440 monitor, disabling the GPU is unacceptably slow

I reinstalled Lightroom CC (2015) and it does not have this issue, I can use GPU acceleration without a problem. 

I bought a new video card (Radeon RX 580) and updated with the latest drivers in an attempt to fix this issue.

Interestingly enough, if I use the crop tool inside develop mode, the photo renders perfectly fine.

Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
It's quite disappointing: This issue is still not entirely fixed in today's LR classic CC 7.2 release.
Seems that in development module it now wirks fine when you switch between images INSIDE a collection. (this also didn't work with LR 7.1)
But when you switch to another collection/folder the black screen phenomenon still appears! :(
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
Still not fixed in LR clasdic CC 7.3

Very very frustrating
Photo of Arnold Bartel

Arnold Bartel

  • 164 Posts
  • 38 Reply Likes
Can anybody confirm that a clean uninstall and install of the video driver did resolve the exactly this issue (black screen in develp mode when GLU on only when switching to another library)?Don't know how often I tried new drivers and clean installs of my Radeon RX470 card => each of them withour success.
I'm somehow tired of replies like "The black screen issue is most likely due to some driver compatibility or bugs. Do a complete clean install the latest GPU driver."Using a 4k display the GPU support is highly necessary for speed reasons and the exact issue description and observations in this thread make it - in my eyes - evident that there is a bug in Lightroom which causes this behavior.
(Edited)