It appears that Chrome's state gets corrupted somehow.
I wasn't able to replicate the issue when running many thousands of your reports, so I'm not sure what will help here.
If you need to run such big batches, perhaps you could use a serverless environment with on-prem jsreport.
Like Azure Container App or AWS Lambda.