Perfect! I tested against 6,500 documents with no orphaned processes. Is it worth considering setting these environment variables as part of the jsreport package? I feel that setting these environment variables should be the default behavior. FYI here's my final implementation:

// Add JS Report for PDF generation.
Environment.SetEnvironmentVariable("chrome_strategy", "chrome-pool");
Environment.SetEnvironmentVariable("chrome_numberOfWorkers", "2");
services.AddJsReport(new LocalReporting()
    .UseBinary(JsReportBinary.GetBinary())
    .KillRunningJsReportProcesses()
    .AsUtility()
    .Create());

Hey guys,

We're having problems with suspended chrome processes which affects the time to generate a PDF document from about 2 seconds per PDF to more than 20 seconds. We are generating about 6,500 documents so this blows out the time to process significantly. I am kicking off the process in Startup.cs using:

services.AddJsReport(new LocalReporting()
    .UseBinary(JsReportBinary.GetBinary())
    .KillRunningJsReportProcesses()
    .AsUtility()
    .Create());

And I have a PdfGenerator class which has the IJsReportMVCService passed in.

internal class PdfGenerator
{
    private readonly IJsReportMVCService _jsReportMvcService;
    private readonly HttpContext _httpContext;
    private readonly RouteData _routeData;
    private readonly HttpRequest _request;

    public PdfGenerator(IJsReportMVCService jsReportMvcService, HttpContext httpContext, RouteData routeData, HttpRequest request)
    {
        _jsReportMvcService = jsReportMvcService;
        _httpContext = httpContext;
        _routeData = routeData;
        _request = request;
    }

    internal async Task<Stream> RenderAsync(
        string content, 
        Orientation orientation, 
        string header, 
        string footer, 
        decimal? marginTopCm = null, 
        decimal? marginBottomCm = null)
    {
        var displayHeaderFooter = !string.IsNullOrEmpty(header) || !string.IsNullOrEmpty(footer);
        
        var report = await _jsReportMvcService.RenderAsync(new RenderRequest
        {
            Template = new Template
            {
                Recipe = Recipe.ChromePdf,
                Engine = Engine.None,
                Content = content,

                Chrome = new Chrome
                {
                    HeaderTemplate = header,
                    FooterTemplate = footer,
                    DisplayHeaderFooter = displayHeaderFooter,
                    Height = "29.7cm",
                    Width = "21cm",
                    MarginTop = displayHeaderFooter 
                        ? marginTopCm.HasValue 
                            ? $"{marginTopCm.ToString()}cm" : "4cm" 
                        : "1cm",
                    MarginLeft = "1cm",
                    MarginRight = "1cm",
                    MarginBottom = displayHeaderFooter 
                        ? marginBottomCm.HasValue 
                            ? $"{marginBottomCm.ToString()}cm" : "2cm" 
                        : "1cm",
                    Landscape = orientation == Orientation.Landscape,
                    MediaType = MediaType.Print
                }
            }
        });

        return report.Content;
    }
}

However when I set up locally I am unable to reproduce this issue, it's only on our prod server. The dotnet application is running using IIS and the IIS version is 10.0.14393.0 running on windows 10 of the same version. It seems to get slower over time meaning it's likely that the number of suspended processes increases over time. Any ideas on this?

Perfect! Thanks so much for this. I do remember reading this a while back but couldn't remember where I saw it.

Hi,

I'm having problems generating PDFs with regards to colours in the headers/footers changing using jsreport.net

I am instantiating the PDF generation using:

var report = await _jsReportMvcService.RenderAsync(new RenderRequest
{
    Template = new Template
    {
        Recipe = Recipe.ChromePdf,
        Engine = Engine.None,
        Content = content,

        Chrome = new Chrome
        {
            HeaderTemplate = header,
            FooterTemplate = footer,
            DisplayHeaderFooter = true,
            // Omitted other config options
        }
    }
});

And the HTML that has been inserted into footer is:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
    <title>Document</title>
</head>
<body>
<div>
    <div style="background-color: purple;">
        <p style="color: #00FFFF">Testing 123</p>
    </div>
</div>
</body>
</html>

When comparing the generated PDF output the colours are different as you can see in this screen grab showing the generated PDF (left) and the same HTML as shown in a web browser (right).

The left image the text colour is #00ABAB where it should be #00FFFF as it is in the HTML. Additionally it fails to show the background colour of purple as set in the div. It's worth noting that HTML content included in the body (content) generates the colours correctly - it seems specifically the header/footer colours that are incorrect, which are a part of the Chrome element. Any ideas?