I filed the EXR crash bug for blender itself (it does seem to be specific to EXR format and doesn’t even need a viewport display to trigger - an equivalent PNG doesn’t crash).
I have been using the build for some heavy duty animation rendering recently. I am seeing reports of BROKEN files in the post-frame report. I’m a little surprised because these are freshly generated tiled EXRs on local storage for each machine and are binary identical when compared :
Machine A (SSD storage):
214 1 1 0.0 0.0s 2048x2048x3.f16 D:\textures\ArMan0004-M4-ArMan0004-M4-Body-D.exr MIP-COUNT[0,0,0,0,0,0,0,0,0,0,0,1]
215 1 5 0.0 ( 4 0.0) 0.0s 2048x2048x3.f16 D:\textures\ArMan0004-M4-ArMan0004-M4-Body-S.exr MIP-COUNT[0,0,0,0,0,0,0,0,0,0,0,5]
BROKEN D:\textures\ArMan0004-M4-ArMan0004-M4-Hair-S.exr
217 1 5 0.0 ( 4 0.0) 0.0s 2048x2048x3.f16 D:\textures\ArMan0004-M4-ArMan0004-M4-Head-D.exr MIP-COUNT[0,0,0,0,0,0,0,0,0,0,0,5]
Machine B (spinning storage)
BROKEN D:\textures\ArMan0004-M4-ArMan0004-M4-Body-D.exr
215 1 6 0.0 ( 2 0.0) 0.0s 2048x2048x3.f16 D:\textures\ArMan0004-M4-ArMan0004-M4-Body-S.exr MIP-COUNT[0,0,0,0,0,0,0,1,0,1,1,3]
BROKEN D:\textures\ArMan0004-M4-ArMan0004-M4-Hair-S.exr
217 1 3 0.0 ( 1 0.0) 0.0s 2048x2048x3.f16 D:\textures\ArMan0004-M4-ArMan0004-M4-Head-D.exr MIP-COUNT[0,0,0,0,0,0,0,0,0,0,1,2]
I noticed that the branch was updated with master, so will try and build that in case it makes things better or more consistent.