The GROMACS simulation stage can "lock" up, being stuck and not returning to the evogrid-simulator surrounding process.
This may not be an infinite loop, some testing suggested with sufficient time this may recover and simulate the frame, or cause GROMACS to abort, which is detected by evogrid-simulator.
This seems to either be caused by randomly seeded parameters causing an impossible to resolve simulation, or by excess bond formation causing the same problem.
Future work to move from evogrid-simulator doing bond formation to GROMACS QM may mitigate this issue.
To see if this has happened to you, watch the output of top . If mdrun has an execution time of multiple minutes, then the simulator is stuck.