Thanks for the report. You do this by shift+clicking in the collection instead. The moment you make the object invisible it gets also unselected, so this is by design at the moment.

Thanks for the report. There is a report somewhere about that already even. Basically this is by design.

It could go either way since in theory with "Local Collections" these objects can still be visible. But I think it is ok to use the view layer visibility flag here.

@Jacques Lucke (JacquesLucke) can you bisect it?

Fixed on rB10162d68e3851.

I cannot reproduce on:

`Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.45

Already got a good public-domain sample file for the initial work, thanks.

I can't reproduce here either (tried the reported version and master). @Brecht Van Lommel (brecht) do you have a backtrace of the crash?

Just for the records, as discussed, the issue with the file requires manual adjustments in the file (In Front or moving the object a bit). This is to be documented in the release log once this feature gets committed.
That said, I get a crash when F12 with said file:

As for everyone pitching in with suggestions for test cases, what is needed are "production" .blend files that were performing better in 2.79 than in 2.80 as far as highpoly mesh editing goes. A cube with subdivision is not a representative of production assets).

Can you see if this patch also fix T73701 (issue prior to color management)?

I see a regression in one of the production files. The cat is in front of the blue shade yet it doesn't show:

Thanks for the report, but this is not a bug. If you flip your normals you get the same result. I guess this is the expected result of the Shader to RGB node.

@Hafeez Dembos (Dembos) what do you get in the console? you should still get a blender_crash.txt, no? (@Sebastián Barschkis (sebbas) aren't you also on Mac?)
Also could you please test with a build from builder.blender.org?

I talked to Pablo and asked him to do a review pass on this as well, to be sure the tools are well integrated with the rest of Blender.

poking @William Reynish (billreynish) for investigation

I find a bit strange that we can preview range and render that preview, so ultimately that is not a preview range but more an "alternative" frame range. Then from the user point of view, how can you tell them apart?

Indeed, definitively a bug, and it happens in final 2.82

Talked to brecht. This still needs confirmation. But if confirmed, then it should be a bug, not a known issue. Just changing the priority for now, waiting for this to be confirmed.