P: Panels and filmstrip black when switching to Develop

The updates are available too. Full roll back instructions are here https://www.lightroomqueen.com/roll-b...

It got so bad I have to revert to a previous version of Lightroom-- but unfortunately only LR CC 2015.0 was made available by Adobe.  Adobe: can you please give us a newer version to revert to while you are fixing this problem?  It is crazy to have to go back 8 versions to fix a problem created in LR CC 2015.8!

I've got the same problem since I installed 2015.8. My computer is fall 2013 27" iMac. I"ve tried disabling the graphics processor, didn't have any impact on panels blacking out. Panels black out regardless of whether I have processor checked or not.  If I click on photos the side panels just go black. I can minimize and bring it back but as soon as I click anywhere it blacks out again. 

Same problem going back and forth between Develop and Library module. I thought it was my computer!@?

Same problem here after updating LR to 2015.8...

Lightroom version: CC 2015.8 [ 1099473 ]License: Creative Cloud
Operating system: Mac OS 10
Version: 10.11 [6]
Application architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 24,576.0 MB
Real memory available to Lightroom: 24,576.0 MB
Real memory used by Lightroom: 6,409.7 MB (26.0%)
Virtual memory used by Lightroom: 8,717.7 MB
Memory cache size: 5,601.2 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Displays: 1) 5120x2880, 2) 5120x2880

Graphics Processor Info: 
AMD Radeon R9 M295X OpenGL Engine

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 4.1 ATI-1.42.15
Renderer: AMD Radeon R9 M295X OpenGL Engine
LanguageVersion: 4.10

Same problem here on an iMac, it's very annoying !!
Can't reaaly work
Was working ok before the last LR update as far as i can remember

Same issue here on Mac Book Pro Retina OS Sierra. Since this morning I had to restart Lightroom 3 times. This makes working impossible, I use Lightroom in my photography studio not only for editing, printing but also to showcase the work at the viewings. Yesterday, it happened at front of my clients 2 times.

I'm seeing this occasionally during a day of processing and several variations thereof. However, I cannot reliably reproduce it. I have GPU acceleration enabled (NVIDIA GeForce GT 750M 2048 MB) on a stock Retina MBP/ Mac OS 10.12.2.

Changing mode seems to be cumulatively involved and I regularly maximise the image during a session with Shift Tab (or L L).

@129856 No it does not. I am also not able to use G / E keys to any effect when the issue is 'live'.

Note: I did not see this in 2015.7

Sometimes, but it happens again straight away, necessitating a restart. I'm quite sure an update is needed, between this and the loss of GPU support for many macs, I don't really know what you are doing at Adobe with LR.

Yes, at least in my experience, but not for long.  The peripheral panes soon black out again in apparent response to subsequent user input.  I haven't taken the time to try methodically to discover a pattern, but my impression is that changing mode from e.g., Library to Develop is very likely to provoke them to go black again while user input within the same mode is less likely to do so.  In any event, the blackout typically recurs within a minute or two after minimizing and restoring.  The fix typically is more persistent when you kill and restart the LR process.  After doing that, I can often work for an hour or more before experiencing this phenomenon, even when cycling among different modes.  So it seems that minimizing and restoring the LR window provokes a temporary restoration of the visibility of the panes along the periphery, but doesn't correct the funny state within LR that caused the blackout in the first place.

By the way, I have never seen this condition occur spontaneously.  In other words, the panes have never blacked out except when I was using the keyboard and mouse.  So it seems as though there is some sort of pathological interaction between a thread that is involved in processing user input and one that is responsible for painting the screen.