The shader probably reached the limit on the number of textures. When this happens the terminal warns that the texture limit in the material has been reached.

Yes, you create a .blend file and reference images, see here:
https://wiki.blender.org/wiki/Tools/Tests/Setup#Render_Tests

In D3789#162680, @Brecht Van Lommel (brecht) wrote:

Can you add tests for these new shader nodes?
Something similar to tests/render/shader/tex_voronoi.blend, a single test that renders with the node in a few different configurations.

Can you add tests for these new shader nodes?

This is a driver-specific problem. The shader probably reached the limit on the number of textures.
When this happens the terminal warns that the texture limit in the material has been reached.
To launching Blender from the Command Line (terminal) in MacOS see https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

Have confirmed was issue with the test image file - hadn't realised that the oiiotool had generated the image with incorrectly labelled channels. Thanks.

Yup.. Unless it changed in 2.82, T72339 [Momentary interface freezes while EEVEE rendering causes progress bar malfunction]:

EEVEE renders in the main thread of blender due to OpenGL limitations. Almost all calls to OpenGL needs to be passed to the driver via the main thread. This halts any other work that is handled by the main thread (python scripts ui updates). Same reason that running python scripts halts UI updates.
The progress status is send to the OS, so here it is updated correctly as the rendering is done by OS threads, not by Blender.

I used to think it is expected..

Fix after gpu refactor in master

In T73760#871193, @Brecht Van Lommel (brecht) wrote:

This channel layout is nonsensical, how to interpret it is probably not defined anywhere.
My advice is to close this as not a bug, it's not worth spending time to support OpenEXR images that don't follow the standard, created with a command line tool.

Pile of Garbage.
Windows and Linux with Intel graphics works perfectly.
Linux have constantly evolving opensource Intel driver.

This channel layout is nonsensical, how to interpret it is probably not defined anywhere.

File rgba.exr opened in gimp has no alpha channel, in krita it does.
Not working in 2.79 as well

Looking at this doesnt help (me at least) much either
If it is just luminace, should this always be read as Alpha?
Maybe @Brecht Van Lommel (brecht) knows?

Natron doesnt recognize the Y.Y channel as Alpha by default either...

For this EXR rgba.exr blender as a whole doesnt seem to be able to read alpha. (not sure yet whether this is correct or not)

@Zoltán András Heiner (Andari) Can you make a screenshot of the new file (so we have something to compare against)?
It looks fine for me on Ubuntu.

@Bryon Leung (GalerkinBunny) please submit a simplified test file.

In T60462#868656, @Jörg Dittmer (NoHow) wrote:

Wow, sounds again like the usual Windows problem with long running computation on the GPU.
Just posted it on another issue a few minutes ago.
If that happens after > 2sec of freezing the GUI , i have a gut feeling that
the Window Timeout Detection and Recovery (TDR) feature is causing this.
SubstancePainter had same issues and they wrote a nice tutorial on how to change the registry values.
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html
I've stumbled accross this problem on various software projects and it often leads to month long bug hunting :(
I'm surprised that the TDR feature is obvousily not well known to most user/deveolpers...
PLEASE SPREAD THE WORD!

Wow, sounds again like the usual Windows problem with long running computation on the GPU.
Just posted it on another issue a few minutes ago.
If that happens after > 2sec of freezing the GUI , i have a gut feeling that
the Window Timeout Detection and Recovery (TDR) feature is causing this.

In T65873#866935, @Clément Foucault (fclem) wrote:

@steve miller (winnertakesteve) Do you get the same behavior if you plug the texture coord/geometry node straight to the material output's volume socket?

This issue does not seem to be limited to drivers, even if I key value of value node, performance is the same.

@steve miller (winnertakesteve) Do you get the same behavior if you plug the texture coord/geometry node straight to the material output's volume socket?

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.