**System Information**
Operating system: Linux-3.10.0-1160.el7.x86_64-x86_64-with-glibc2.17 64 Bits
Graphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80
**Blender Version**
Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-06-02 21:50, hash: `rB1fb36e9a7c67`, 3.2, any
Worked: none
**Short description of error**
There is a type of exr coming from Renderman which is cropped to content in Blender compositor. I don't know how it's being produced, but if you have empty pixels they will be cut out and the resulting image will be of a smaller resolution than the image should be. This behavior makes it unusable for compositing as the resolution will jump around as camera moves and the area of the empty space varies, for example.
Nuke is able to handle this. It just shows you the cut region, but keeps the image intact.
The image in this example is 2048x858
Here is the Blender exr reading
{F13133483}
And the Nuke's
{F13133487}
And for some reason the cropped resolution in Blender is 1px off compared to Nuke from some reason. But maybe it's an another issue.
Btw Natron handles this exr just like Nuke does.
UPD: I found that it's NaNs and Blender just cuts them off, hence changing the resolution.
**Exact steps for others to reproduce the error**
Open the attached file in the compositor
{F13133496}