The case would be instead of sending a json with millions of lines, "split" that json into several and send these jsons through my API (C#)
And so it would probably avoid timeout and memory errors
R
Posts made by rfmo94
-
RE: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryposted in general forum
-
RE: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryposted in general forum
there is possibility to have multiple json files in a single template?
-
templating enginesposted in general forum
No templating engines strategy: it had http-server and I changed it to dedicated-process because I saw it in a forum topic
-
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryposted in general forum
I leave here the link of my json , where you can see that I have a lot of data. And it is recurring that I have reports with this size, due to the many transactions
https://we.tl/t-LzeybgDoSwMy jsreport.config
My package
I've tried on another machine to put the latest version of jsreport but I have the same problem.
The errors that usually appear to me are Payload to large, heap out of memory
Any solution you recommend? Because I have several clients that need long reports, as in this case
-
How to update jsreport for version 3.0?posted in general forum
I need updated my version of jsreport , because html-to-xlsx not opening in current version.
How can i update?
