Allowed memory size of - bytes exhausted using puphpeteer v2.4.1 and zoonru/rialto ^1.6

[kksonthomas]

Describe the bug
I am using puphpeteer and one day my crawler not longer working with memory exhausted error.
After some checking, i noticed that problem occurred after composer update to latest version of puphpeteer and rialto

Reproducible example

$puppeteer = new Puppeteer(['executable_path' => __DIR__ . '/../../../node_modules/node/bin/node']);
        return $puppeteer->launch([
            'headless' => true,
            'executablePath' => '/usr/bin/chrome-linux/chrome',
            'args' => [
                // cache
                '--disable-dev-profile',
                '--aggressive-cache-discard',
                '--disable-cache',
                '--disable-application-cache',
                '--disable-offline-load-stale-cache',
                '--disable-gpu-shader-disk-cache',
                '--media-cache-size=0',
                '--disk-cache-size=0',
                // performance
                "--disable-infobars",
                "--no-sandbox",
                "--disable-gpu",
                '--disable-setuid-sandbox',
                '--no-zygote',
                "--disable-web-security",
                "--disable-extensions",
                "--disable-plugins",
                "--headless",
                "--disable-breakpad",
                "--disable-client-side-phishing-detection",
                "--disable-sync",
                "--disable-translate",
                "--no-experiments",
                '--disable-default-apps',
                '--mute-audio',
                '--no-default-browser-check',
                '--disable-background-timer-throttling',
                '--disable-backgrounding-occluded-windows',
                '--disable-notifications',
                '--disable-background-networking',
                '--disable-component-update',
                '--disable-domain-reliability',
                '--autoplay-policy=user-gesture-required',

                '--disable-component-extensions-with-background-pages',
            ]
        ]);
    }

above is the launch codes as ref.
note that the code is running fine in
puphpeteer v2.4.0
zoonru/rialto 1.5.5

Expected behavior
Successful run without any exception thrown

Exception thrown

Whoops\Exception\ErrorException 
…/vendor/clue/socket-raw/src/Socket.php:263
1
Whoops\Run handleError
…/vendor/filp/whoops/src/Whoops/Run.php:520
0
Whoops\Run handleShutdown
[internal]0

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-143-generic aarch64)
• Node version: v22.16.0
• PHP version: 8.3.22

My Node package manager is:

• NPM (10.9.2)

Additional context
Add any other context about the problem here.

[xtrime-ru]

This code works for my with latest versions or rialto (1.6.4) and puphpeteer. Please make sure you updated composer and npm and try again.

[ValCanBuild]

I'm having a similar issue - getting OOM on the latest version (puphpeteer 2.4.1 and rialto 1.6.5)

[2025-09-05 10:13:53] local.INFO: Applying options... {"options":{"read_timeout":60,"log_browser_console":true,"js_extra":"","idle_timeout":100,"logger":{"Illuminate\\Log\\Logger":[]}}} {"tenantId":1}
[2025-09-05 10:13:53] local.DEBUG: Options applied and merged with defaults {"options":{"executable_path":"node","idle_timeout":100,"read_timeout":60,"stop_timeout":3,"logger":{"Illuminate\\Log\\Logger":[]},"log_node_console":false,"debug":false,"log_browser_console":true,"js_extra":""}} {"tenantId":1}
[2025-09-05 10:13:53] local.INFO: Starting process with command line: 'node' '/var/www/main/node_modules/@zoon/rialto/src/node-process/serve.js' '/var/www/main/vendor/zoon/puphpeteer/src/PuppeteerConnectionDelegate.js' '{"idle_timeout":100,"log_node_console":false,"log_browser_console":true,"js_extra":""}' {"commandline":"'node' '/var/www/main/node_modules/@zoon/rialto/src/node-process/serve.js' '/var/www/main/vendor/zoon/puphpeteer/src/PuppeteerConnectionDelegate.js' '{\"idle_timeout\":100,\"log_node_console\":false,\"log_browser_console\":true,\"js_extra\":\"\"}'"} {"tenantId":1}
[2025-09-05 10:13:53] local.INFO: Process started with PID 876 {"pid":876} {"tenantId":1}
[2025-09-05 10:13:53] local.DEBUG: Sending an instruction to the port 38729... {"pid":876,"port":38729,"instruction":{"type":"call","name":"connect","catched":false,"value":[{"browserWSEndpoint":"ws://app_headless_chrome:3000/chrome?launch=%7B%22args%22%3A%5B%22--no-sandbox%22%2C%22--disable-gpu%22%5D%2C%22headless%22%3Atrue%7D"}]}} {"tenantId":1}
[2025-09-05 10:13:53] local.ERROR: Allowed memory size of 134217728 bytes exhausted (tried to allocate 808464464 bytes) {"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Allowed memory size of 134217728 bytes exhausted (tried to allocate 808464464 bytes) at /var/www/main/vendor/clue/socket-raw/src/Socket.php:263)
[stacktrace]

[xtrime-ru]

@ValCanBuild Increase memory_limit for your script. 128 megabytes is not enough.

[ValCanBuild]

I tried 256, 512 and it stopped throwing an error at 1GB - that looks like way too much?

In any case, it doesn't fix it because I then get a timeout error

local.ERROR: Error in /var/www/main/vendor/zoon/rialto/src/ProcessSupervisor.php, Line 372: The timeout (60.000 seconds) has been exceeded while reading the socket of the process. Maybe you should increase the "read_timeout" option.  {"tenantId":1}

[xtrime-ru]

@ValCanBuild Can you send code to reproduce the issue?
And make sure you updated both js and php versions of rialto.

[ValCanBuild]

Isn't the JS version just:

"@zoon/puphpeteer": "git+https://git@github.com/zoonru/puphpeteer.git#zoon",

[xtrime-ru]

Yes, but js and php parts of package are updated with different commands (composer/npm). It's easy to end up with different versions of js/php parts. Versions mismatch will cause weird bugs.

[xtrime-ru]

@kksonthomas Can you check latest zoonru/rialto v1.6.6?
Here is change log: zoonru/rialto@v1.6.5...v1.6.6

Update:
composer update && npm update

[kksonthomas]

@kksonthomas Can you check latest zoonru/rialto v1.6.6? Here is change log: zoonru/rialto@v1.6.5...v1.6.6

Update: composer update && npm update

updated to:
zoon/rialto (v1.6.6)
zoon/puphpeteer (v2.4.2)
node (v22.21.1)

and problem still exists

However, i recently deployed my project on a Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-164-generic x86_64)
and it works fine with updated version of zoon/rialto and zoon/puphpeteer.

So the problem for me seems related aarch64 server and / or specific version of chome for aarch,

[kksonthomas]

@kksonthomas Can you check latest zoonru/rialto v1.6.6? Here is change log: zoonru/rialto@v1.6.5...v1.6.6
Update: composer update && npm update

updated to: zoon/rialto (v1.6.6) zoon/puphpeteer (v2.4.2) node (v22.21.1)

and problem still exists

However, i recently deployed my project on a Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-164-generic x86_64) and it works fine with updated version of zoon/rialto and zoon/puphpeteer.

So the problem for me seems related aarch64 server and / or specific version of chome for aarch,

So after i try my dev env with updated versions of lib above mentioned:

1. downgrade back to puphpeteer v2.4.0 and zoonru/rialto 1.5.5
2. now the crawler no longer working with new Error:
   Call to a member function newPage() on null
   It is happens on the line trying to call the function of the object returned by $puppeteer->launch
3. chown the vendor folder back from root to user
   chown -R admin:admin vendor/
4. restart all related service (dont think it is helpful)
5. update back to puphpeteer v2.4.2 and zoonru/rialto 1.6.6

and now it works on new lib, even the memory exhaust problem gone

I really dont know what happens so i just share here to discuss
And sorry it seems not related to aarch or x86_64

[kksonthomas]

@kksonthomas Can you check latest zoonru/rialto v1.6.6? Here is change log: zoonru/rialto@v1.6.5...v1.6.6
Update: composer update && npm update

updated to: zoon/rialto (v1.6.6) zoon/puphpeteer (v2.4.2) node (v22.21.1)
and problem still exists
However, i recently deployed my project on a Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-164-generic x86_64) and it works fine with updated version of zoon/rialto and zoon/puphpeteer.
So the problem for me seems related aarch64 server and / or specific version of chome for aarch,

So after i try my dev env with updated versions of lib above mentioned:

1. downgrade back to puphpeteer v2.4.0 and  zoonru/rialto 1.5.5

2. now the crawler no longer working with new Error:
   `Call to a member function newPage() on null`
   It is happens on the line trying to call the function of the object returned by $puppeteer->launch

3. chown the vendor folder back from root to user
   ` chown -R admin:admin vendor/`

4. restart all related service (dont think it is helpful)

5. update back to puphpeteer v2.4.2 and  zoonru/rialto 1.6.6

and now it works on new lib, even the memory exhaust problem gone

I really dont know what happens so i just share here to discuss And sorry it seems not related to aarch or x86_64

Tried to update my arrch prod, memory exhausted
downgrade back, working again

I really dont know how to debug now

Edit: okay i forgot to update node
After updated the node the exhaust memory problem gone with latest library

The version of node is v22.21.1
when updating my node i have notice a warning might be related:

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

[ValCanBuild]

I can confirm this still happens intermittently on the latest versions - even when using node 22.21.1

@kksonthomas how did you get it working?

[ValCanBuild]

This is still a major problem. Any updates?

[xtrime-ru]

This is still a major problem. Any updates?

No updates from us, because we dont experience any issues with memory in our production environment.

@ValCanBuild Can you provide Dockerfile which reproduces the issue?