Allowed memory size exhausted due to No such entity exception

Bilalyounas1234 commented 1 year ago

Summary

After upgrading the Magento version to 2.4.3p1 we are facing (No such entity exception) issues and due to this our server goes down and then we need to restart all services. We checked some time this error occurs while product search sometimes on checkout and sometimes on any other request.

Logs in nginx due to this issue:

[error] 107960#107960: 3469139 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4194312 bytes) in /data/site/vendor/magento/framework/Exception/NoSuchEntityException.php on line 50" while reading response header from upstream, request: "GET /en/catalogsearch/result/?q=Prime HTTP/1.1", upstream: "fastcgi://127.0.0.1:9004", host: "site", referrer: "https://site/en/catalogsearch/result/?q=Sunscreen+" [error] 107960#107960: 3469131 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4194312 bytes) in /data/site/vendor/magento/framework/Exception/NoSuchEntityException.php on line 50" while reading response header from upstream, request: "GET /en/popup/ajax/addCookie/?isAjax=true&form_key=RYfvz8vlQ4fNnbG4&cookie_type=aw_popup_viewed_page&current_url=https%3A%2F%2Fsite%2Fen%2Fcms%2Findex%2Findex%2F HTTP/1.1", upstream: "fastcgi://127.0.0.1:9004", referrer: "https:/site/site/en/"

Examples

[error] 107960#107960: 3469139 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4194312 bytes) in /data/site/vendor/magento/framework/Exception/NoSuchEntityException.php on line 50" while reading response header from upstream, request: "GET /en/catalogsearch/result/?q=Prime HTTP/1.1", upstream: "fastcgi://127.0.0.1:9004", host: "site", referrer: "https://site/en/catalogsearch/result/?q=Sunscreen+" [error] 107960#107960: 3469131 FastCGI sent in stderr: "PHP message: PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4194312 bytes) in /data/site/vendor/magento/framework/Exception/NoSuchEntityException.php on line 50" while reading response header from upstream, request: "GET /en/popup/ajax/addCookie/?isAjax=true&form_key=RYfvz8vlQ4fNnbG4&cookie_type=aw_popup_viewed_page&current_url=https%3A%2F%2Fsite%2Fen%2Fcms%2Findex%2Findex%2F HTTP/1.1", upstream: "fastcgi://127.0.0.1:9004", referrer: "https:/site/site/en/"

Proposed solution

No response

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[X] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 1 year ago

Hi @Bilalyounas1234. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

m2-assistant[bot] commented 1 year ago

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
[ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Bravo commented 1 year ago

Hi @Bilalyounas1234,

Thank you for reporting and collaboration.

Please try to increase memory size. your PHP.ini settings, in this case is the memory_limit

use this commands

php -dmemory_limit=-1

bin/magento setup:di:compile

bin/magento setup:static-content:deploy

Kindly let us know if you are still facing any issue.

Thanks.

engcom-Bravo commented 1 year ago

Hi @Bilalyounas1234,

Please provide us latest update on this comment https://github.com/magento/magento2/issues/37594#issuecomment-1584038647 and if you are still facing any issue kindly refer this document https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/php-settings.html?lang=en regarding PHP settings.

Thanks.

engcom-Bravo commented 1 year ago

Hi @Bilalyounas1234,

We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

magento / magento2