Yes, the jsreportonline runs an old version. The problem is the turbulent chrome changes. We can't simply update without affecting existing users' layouts. We are not sure how we will get through this yet, but internal discussions are ongoing.
If you need later fixes now, you'd better switch to the on-prem version.
Thanks for sharing. Yes, Chrome may have some issues due to limited hardware.
jsreportonline has currently allocated 1.5 CPU and 2048 + 2560(SWAP) MB for every rendering container.
Unfortunately, that is not possible. jsreportonline doesn't allow altering the server config.
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.
Thanks for posting. We have now analysed it more deeply.
The problem is that with an empty cell, we still render an empty tag (<v></v>) to the Office XML, which prevents the overflow from the previous cell.
We will fix this here
https://github.com/jsreport/jsreport/issues/1242
I apologize for the delay. I had to make sure Azure broke things really badly...
Unfortunately, Azure changed the libraries installed in the Azure Functions runtime. This affected Chromium, which currently doesn't work there. The only option is to use Docker or a premium plan and install the missing libs.
However, the better option is now to use Azure Container Apps. This lets you serverless host jsreport in a container with no missing lib issues.
I've updated docs and added this tutorial on how to get started with running jsreport in the Azure Container App.
https://jsreport.net/learn/azure-container-apps
Please share a minimal playground demo replicating the issue.
https://playground.jsreport.net/
One credit is 1 second spent in the container that is processing your request. It is calculated based on milliseconds.
It is replanishing based on your renewal date. Check the "created on" field in the settings of your profile.
The studio browser requests are free of charge so you are free to play with your worskspace as much as needed.
Will we see a significant performance increase when we switch to the paid version?
No, the containers are the same.
Could this timeout be related to the jsreport.npm.require?
Yes, this signals that the npm install of the module timed out.
This can be some kind of transient network/npm error.
It seems to work fine for me also in your account, please try later again.