Hi @Ish-Modi

It will be part of the next release 4.12.0 which should be live within two weeks.

Hi,

The fix is already in the master branch. I expect the release to happen within the next two weeks.

However, you can easily already apply the fix manually, it is just one line change
https://github.com/jsreport/jsreport/commit/b7c97212ca1bb7eba65475cdab7432e6fec4996f

That is very hard to tell. It could be a Chromium leaking bug causing it to become stuck.
Have you checked the memory consumption? Isn't Chromium leaking and growing the memory endlessly?
What if you try to loop and render those 6000 requests locally? Does it show the same behavior?
Check the /tmp and /dev/shm usage, isn't it getting full?

Perhaps setting config chrome.strategy=dedicated-process could help you.
This will ensure you have a fresh new instance of Chromium every time you render the request.

Thank you for reporting the problem.
I was able to isolate the issue. The latest Chromium interprets one of the configurations we use differently, which breaks the limited AWS Lambda runtime. We will try to reimplement the approach. Hopefully, it will be part of the next release. However, we still need to analyze the new approach, so no promises yet.

Here is the bug to track
https://github.com/jsreport/jsreport/issues/1271

Thank you for the template. We're gonna check if we can optimize processing a bigger XLSX template like this one
https://github.com/jsreport/jsreport/issues/1270

We will again update puppeteer/chromium in the next release. As always. Likely soon.

If you need to update just now, go ahead and update the puppeteer dependency.
You just need to list the latest puppeteer dependency in your package.json.

Or build your own Docker image with the updated Chromium. However, note that the latest Chromium with the fix is not yet in the public repository at the time of writing this post.

Unfortunately, this isn't supported yet.
I've added this feature to the backlog now
https://github.com/jsreport/jsreport/issues/1269

Yes, thanks. Done...

Hi,

Unfortunately, we don't provide a compiled version of jsreport in the latest release. There is a problem with the technology used for compilation. We will try to support the compiled versions again in the next release.

I've updated the release notes. I apologize for the confusion.

Jan

Unfortunately, it's not there. There was some controversy, but I am adding this now...