Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Actor does not release memory

See original GitHub issue

Describe the bug In 2 different actors with PuppeteerCrawler there is problem, that if we kick off runs with Chrome, after some time currentConcurrency go down to 1 and memory usage is still growing:

launchContext: {
    useChrome: true,
    launchOptions: {
        stealth: true,
        headless: false,
        devtools: false,
    },
},

We also tried set lower closeInactiveBrowserAfterSecs:

browserPoolOptions: {
    closeInactiveBrowserAfterSecs: 120,
}

but it not help.

Once we set:

launchContext: {
    useChrome: false,
}

it is working correctly. It is happening after upgrade to node 16 and SDK 2.0.

System information:

OS: docker apify/actor-node-puppeteer-chrome:16
Node.js version 16
Apify SDK version 2.1.0

Issue Analytics

State:
Created 2 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

B4nancommented, Nov 23, 2021

Nope, this was addressed only on platform, no fix in the sdk code directly. We basically disallowed the creation of core dumps inside docker.

1reaction

B4nancommented, Nov 15, 2021

There are no errors visible in the log, just regular page handler timeouts. At it looks like they are generated regardless of such errors, so my guess is it happens when we try to close the browser (as it has no effect on the running crawler and no errors are printed anywhere).