Laravel 12 vs 8 issue

[itx-ag]

Hi,

I have a project that is in laravel 8 and php 8.1 in production.

We currently are migrating the project to laravel 12 and php 8.4 and we deployed it to the develop and staging environment and currently testing.

Our hosting provider enables the NewRelic agent when we set a env variable, and it is enable for all environments. We do not have custom code regarding NewRelic in our code. We did not change NewRelic agent configuration since this is the hosting provider configuration.

In staging and production the PHP memory is limited to 512MB, even CLI. We have an artisan command to go through our DB data and generate OpenSearch documents. This is a long running command that takes around 2 hours and is only ran manually when needed. It loop through the DB data using https://laravel.com/docs/12.x/eloquent#chunking-results and then inserts the documents in OpenSearch using bulk api (https://docs.opensearch.org/latest/api-reference/document-apis/bulk/).

What I've noticed when we upgrade the project and we run the cli command in staging, after a while it reaches the php memory limit and kills the command.

Then I ran the command with:

-d memory_limit=10000M
It finishes running the command but the php process reaches around 4.5GB.

After some debugging I ran the same command with:

-d newrelic.enabled=0
The memory does not go over 60MB indicating a problem with the new relic extension / agent.

I cannot run the same in production right now, but I ran it a few months back and we did not have the same php memory limit problem. I do remember in production that in the middle of the process I would get a warning message on the screen from NewRelic extension / agent saying that it would stop tracking (can remember the exact words). This message does not show up in staging.

In Production we have the following versions:

• php 8.1.31
• laravel 8
• newrelic agent 11.4.0.17

In Staging we have the following versions:

• php 8.4.10
• laravel 12
• newrelic agent 11.10.0.24

Although I can run the command without NewRelic being enabled it worries me what will happen on php cli processes we are always running like Laravel queue workers and processes that run from time to time like laravel scheduler and other cron jobs.

I see that new relic agent still does not have support for laravel 12? Could this be the problem?

Thank you,
Pedro

PS. I labeled it as a bug but don't know if it is correct label

[newrelic-php-agent-bot]

Thank you for your issue report. A member of the New Relic PHP Agent Team will review your report and endeavor to respond in a timely manner.
Need troubleshooting help? Please review some of our common troubleshooting documentation, starting with generating debug logs. From there, additional resources and tips are available in our troubleshooting section, accessible from the left-hand panel of our documentation site. Additionally, please be sure to visit our Explorer's Hub, where other members of the community may have solved an issue similar to yours with the help of our Support team members.
Have a question regarding support for an Operating System, PHP Version, Framework, or Library? Please take a look at our Compatibility Docs.
Binary support for ARM-based CPU architecture is now available via the tarball installation method for PHP Versions 8.0+!
General installation instructions can be found on our Installation Overview page.
Need more information about an Agent INI setting? Our Configuration page contains an explanation for each INI setting and how to modify the defaults.
Looking for something else? All New Relic PHP Agent Documentation can be found under our Introduction page.

[zsistla]

We recommend breaking up long-running transactions to avoid mem situations like you are describing above.
Please try the instructions in this doc for more details on how to break the transaction up.

If this does not solve your issue, we'll need you to reach out to our support team so we can gather more info required to debug.

[newrelic-php-agent-bot]

This issue has been identified as requiring additional information to debug. Due to the potentially sensitive nature of the information we may have to collect, such as PHPInfo and Debug Logs, please follow these steps to create a support case, where a member of our New Relic Support Team will work with you to gather the necessary information securely and help debug your issue.
If your subscription level does not include technical support, the other option available to customers is to use New Relic’s community support channel: Explorers Hub. From there, a member of our New Relic Support Team will work with you to gather the necessary information securely and help debug your issue. For all available options on how to get support, please see these resources.