Please check here
https://playground.jsreport.net/w/anon/QLkuZ0EP

I'm not an expert on fonts, but maybe the following trick will solve your problem

<style>
      body {
          zoom: 1.5;                
      }
</style>

Note that the font handling is processed fully by Chrome and jsreport does not influence it.

This needs to work... Are you configuring that newer 4.6 jsreport? Are you sure your config file is properly applied? Have you restarted jsreport?

I've tried the following...

• Windows 11 OS
• Download 4.8.0 jsreport.exe binary https://github.com/jsreport/jsreport/releases/tag/4.8.0
• Download nssm 2.24 x64 exe binary
• Place both to the same dir
• run nssm install jsreport
• in the form I fill path to the dir and add start argument
• I open the studio localhost:5488 and let it create sample reports
• Then I render in the loop 1000 reports

const client = require('@jsreport/nodejs-client')('http://localhost:5488')

async function run () {
  for (let i = 0; i < 1000; i++) {
    await client.render({
      template: {
        name: 'invoice-main'
      }
    })
    console.log('rendered', i)
  }
}

run().then(() => console.log('done')).catch(err => console.error(err))

In the taskmanager I see ~ constant number of chrome processes

The default number of worker threads jsreport uses is 2. Therefore, I see 2 main chrome processes and several nested chrome processes which chrome uses. If you use the same approach, do you get different observations?

Note if you want to let jsreport close the chrome processes after every render, you can create file jsreport.config.json and add the following

{
  "chrome": {
    "strategy": "dedicated-process"
  }
}

I don't think this could have anything to do with jsreport configuration.
Doesn't your report do remote calls? Let's say you are fetching some remote data or images?

For the development environment, you can use the following configuration. This will allow you to use the same license key as you have in prod without warnings.

{   
    "license": {
        "development": true
    }   
}

Every other production instance needs a new license key. Or you can purchase the more expensive scale license, which provides a license key that can be used on infinite instances.

Yes, we will try to update it with the next release, it shouldn't be problem.
Only the compiled jsreport binary could be a problem so it may take more time.

That is task for the jsreport asset.

In jsreport script, you can require the function from asset like this
https://jsreport.net/learn/assets#require-asset

I don't understand the question...
If you have a single instance license key, you can use it just in the single jsreport app.

Please share a minimal playground demo replicating the issue.
https://playground.jsreport.net/