![]() Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.#Magento 2 set private cache professional Vendor/magento/module-csp/Model/BlockCache.php The result would get cached and stay in the cache until the redis cache was cleared.Īfter a lot of digging I found the source of the issue in: We found out via SSH top that the RAM consumption was peaking during the category generation on the frontend (from uncachd to cached).įirst we thought it was a Redis issue because 9 out of ten times the page would look broken like we have seen in the M1 days because of a Redis issue.īut actually "the broken page layout" was the result of PHP running out of memory. This function uses a crazy amound of RAM. Quick workaround is disabling the module to keep the shop RAM usage healthy. ![]() The log errors show that this function is causing issues. ![]() PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 45056 bytes) in Unknown on line 0, referer: PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 20480 bytes) in /var/on line 42 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 65536 bytes) in Unknown on line 0 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 4096 bytes) in /var/on line 108 PHP Fatal error: Allowed memory size of 792723456 bytes exhausted (tried to allocate 48238592 bytes) in /var/www/html/vendor/magento/framework/Serialize/Serializer/Json.php on line 24 I copied the log errors from another user running into the same issue:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |