Posts made by admin

See this config
https://jsreport.net/learn/configuration#workers
https://nodejs.org/api/worker_threads.html#worker_threads_worker_resourcelimits

Could you please let us know the default heap size?

These are the runtime/nodejs settings.
Each thread gets the same default limit as the main thread
~1.5 GB on 64-bit systems

How many percentage of RAM should be allocated to heap?

There is no rule of thumb, try what works best for you.
The main thread can remain in default, and the rest can be divided among workers.

If we have set only one worker then why are we getting heap size limit issue?

Because every worker has the nodejs default limit.

Do references held by previous renders get freed up after report rendering finishes?

nodejs is the garbage-collected runtime. So it gets cleaned from memory when the GC gets triggered by the runtime.

Hi, it is likely that in June 2026, the node VM module will enable us to sandbox ESM modules.

However, note that in the newer node, you will still be able to use CommonJS modules as of now.
In other words, that date, June 2026, shouldn't be significant for you.

This hasn’t been implemented yet, unfortunately — there were other priorities.

The xlsx recipe, when you use xlsxAdd, already use batching and streaming internally.
Do you hit an OOM error when having many rows?

Would you be able to email me the mentioned pdfs?

You can send the export or compressed data folder...

I cannot imagine why the perf would be different when using external config. Maybe some kind of disk virtualization/docker/os issue.

Anyway, what if you test things without Docker first and then troubleshoot the containerization issues?

You have two loops in your folder structure.

folder with shortid 0HYiJb9 has parent itself
folder AKH3fuS has a parent 2vof8k_ which has parent AKH3fuS

To fix your workspace
set to the folder with shortid: 0HYiJb9 the prop folder null to move it to the root
and set to the shortid: 2vof8k_ the prop folder to null

I am not sure how this happened. If you will ever be able to deterministically replicate this, we will happily take a look.

why handlebar and chrome pdf took this much of time , any idea ?

The only thing that comes to my mind is that the reason is a super throttled CPU.
Try a different machine, or send me your workspace I can test.

There is no extra setting. Try to compare the profile, what is actually the bottleneck
https://jsreport.net/learn/studio#profiles

Regarding the original question...
It appears that the studio's JavaScript is freezing the browser. Would it be possible for you to share with me confidentially your workspace? An export or a mongodb dump. You could clean all the data and template content if you need to. You can email me a link where to download it to jan.blaha@jsreport.net

Regarding rendering time...
The jsreportonline has limited containers, so your full machine env should actually be faster.
One thing that comes up to my mind is that the problem could be amount of entities -> slow db and loading.
Could you check your collections have indexes? The latest jsreport automatically creates indexes.

Could you check F12 network/js dev tools? Is there an error, or just some requests hanging?
Any errors in the standard server log?

Hi,

We will update the deps to provide a clean audit report during the next release. As always...

We don't have a date yet, though.

You can see these warnings in the profile output

The highcharts CDN blocks the request to download the script.
It is the same problem described here, please check the mentioned solutions.
https://forum.jsreport.net/topic/3473/pdf-generation-err_blocked_by_orb/2

Have you tried to disable the charts animations?

Yes, jsreport needs to be restarted after every configuration change.

Please check the following
https://jsreport.net/learn/reports#cleanup

I'm not sure if I understand the question.
However, if you mean you want to specify in the rendering request the full path of the template, then yes, you can do it like this.

{
  "template": { 
      "name": "/folderA/subfolder1/subfolder2/subfolder3/template1" 
  },
  "data": {}
}

This is the right config,
express.enabled: true, studio.enabled: false
However, in v2 there is still login screen wired, you would need to update jsreport.

Or you can overwrite the route in your server.js file

const jsreport = require('jsreport')()

if (process.env.JSREPORT_CLI) {
  // export jsreport instance to make it possible to use jsreport-cli
  module.exports = jsreport
} else {
  jsreport.init().then(() => {
    reporter.on('after-express-static-configure', (app) => {    
      app.get('/', (req, res) => {
        res.status(404).send('Not Found')
      })
    })
    // running
  }).catch((e) => {
    // error during startup
    console.error(e.stack)
    process.exit(1)
  })
}

It gets applied for me.
I can set marginTop in script and also in the studio.

It seems like your stored data got a bit corrupted, maybe with some custom ODATA calls?

There should be no @odata stored in the db, that is likely causing the issue.
Can you please try to find which odata call adds that attribute to the entities?
Thank you

That script triggering the print with window.JSREPORT_READY_TO_START would need to be in that stock-market page. This means your template will just wait until it times out.

You can try waiting for the network instead