RADF output causes a crash when assigning more than one mesh per MPI process

[tstopi]

Describe the bug
The attached simple test case with RADF output fails with "access violation" error when executed serially, but runs fine when executed with MPI. In general this seems to be an issue if you have more than one mesh per mpi process and one of the meshes contains an RADF line
Cases were run on FDS-6.11.1-0-gff928db-release

To Reproduce
&HEAD CHID='RADF-Test'/
&TIME T_END=10.0/
&DUMP DT_DEVC=1.0, DT_HRR=1.0, DT_PL3D=10.0, DT_SLCF=10.0, DT_SL3D=30.0, DT_RESTART=5000.0, DT_RADF=1.0/
&MISC TMPA=20.0/
c All Meshing options fail with serial FDS
c This works with mpiexec -n 3
c&MESH ID='Room_01', IJK=20,40,32, XB=0.0,2.0,0.0,4.0,0.0,3.2/
c&MESH ID='Room_02', IJK=20,40,32, XB=2.0,4.0,0.0,4.0,0.0,3.2/
c&MESH ID='Room_03', IJK=20,40,32, XB=4.0,6.0,0.0,4.0,0.0,3.2/

c This works with mpiexec -n 2
c&MESH ID='Room_01', IJK=20,40,32, XB=0.0,2.0,0.0,4.0,0.0,3.2, MPI_PROCESS=0/
c&MESH ID='Room_02', IJK=20,40,32, XB=2.0,4.0,0.0,4.0,0.0,3.2, MPI_PROCESS=1/
c&MESH ID='Room_03', IJK=20,40,32, XB=4.0,6.0,0.0,4.0,0.0,3.2, MPI_PROCESS=1/

c This fails with mpiexec -n 2
&MESH ID='Room_01', IJK=20,40,32, XB=0.0,2.0,0.0,4.0,0.0,3.2, MPI_PROCESS=0/
&MESH ID='Room_02', IJK=20,40,32, XB=2.0,4.0,0.0,4.0,0.0,3.2, MPI_PROCESS=0/
&MESH ID='Room_03', IJK=20,40,32, XB=4.0,6.0,0.0,4.0,0.0,3.2, MPI_PROCESS=1/

&RADF XB=0.5,1.5,2.0,3.0,2.5,2.8, I_STEP=1, J_STEP=1, K_STEP=1/ Problem_1

Desktop (please complete the following information):

• OS: Windows 11
• Version: 25H2

[mcgratta]

I'll take a look.

[mcgratta]

Try the latest source code. This is a rarely used feature, so I am sure there might be other bugs in it. Close the Issue if it works.

[tstopi]

Thanks Kevin. I will test the next nightly build and close this if it works

[tstopi]

Seems to work with the latest nightly build