Just for update, I could not find the root of the error but when I install ParaView with osmesa support rather then egl. I could able to run the simulation and I am not getting invalid error. Maybe it was related with the egl setup not sure. But, now since I am using osmesa, I am getting following common rendering error.
3: double free or corruption (fasttop)
4: double free or corruption (fasttop)
5: double free or corruption (fasttop)
2: double free or corruption (fasttop)
The osmesa is fine under Github ubuntu runner and produces correct output but under HPC platform I have no luck with osmesa. So, I think the ultimate solution is to make EGL work in here. Anyway, I’ll keep workin on it.
Just to update about this issue in case of somebody else hit similar issue. Tested with osmesa backend with gcc/13.3.0 (again all installed with spack) and it seems it is working fine except following error when it is rendering,
2: ( 42.387s) [pvbatch.0 ] vtkTextureObject.cxx:1108 ERR| . . vtkTextureObject (0x3ab085f0): Attempt to use a texture buffer exceeding your hardware's limits. This can happen when trying to color by cell data with a large dataset. Hardware limit is 65536 values while 260020 was requested.
This error is orthogonal to this issue but it seems it is related with the mesa version used to build paraview (Texture buffer size error - Support - VTK). I was using mesa@23.3.6 in my spack installation. So, I’ll try with newer version of mesa library (i.e. * 25.0.5) to see if it helps.
Anyway, my pipeline is working fine except output figure does not have color map (only vectors) and it does not give error like double free or corruption (fasttop) when it is compiled with intel compiler (oneapi-2024.2.1). It seems that it is compiler issue. I’ll also try gcc with egl backend to see what happens and also mesa with newer version.
@ben.boeckel It seems that mesa needs to be build with llvm support to get rid of texture buffer size. If you disable llvm it fails with limit error. I am not sure what is wrong with the mesa library but at this point I could able to render without any issue. The only minor thing is that since mesa build with llvm support it requires first loading llvm module and then I am loading gcc module to prevent runtime issue. the module system complains able llvm dependency of the mesa library but the code works fine. BTW, I am using spack package manager to build all the required libraries. @cory.quammen Let me know if you have any idea.