Advanced Search

Hello,

you are right, when i disable Serials, i get this error again:


Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/breisig.live/www/htdocs/libraries/src/Log/LogEntry.php on line 126

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/breisig.live/www/htdocs/libraries/vendor/symfony/error-handler/Error/OutOfMemoryError.php on line 1

So i will search for it on another way.

Hello,

Please disable the plugin "HikaSerials - HikaShop Integration plugin" in your Joomla backend.
Then, perform a new test in your checkout.

Regarding the error message, we have not information on which "elements" is using too much memory, but the issue occurs in the Log System, not in HikaShop or HikaSerial.
Nevertheless, increasing the memory limitation in your hosting could be a good solution.
Specially if you are trying to generate big images with the "attach serial" plugin ; that kind of processing need to load the entire image (uncompressed) in memory in order to modify it with the rest of the content.

Regards,

-- HikaShop version -- : 5.1.6
-- HikaSerial version -- : 5.0.0
-- Joomla version -- : 5.3.0
-- PHP version -- : 8.4.6
-- Browser(s) name and version -- : FF 138.0.4
-- Error-message(debug-mod must be tuned on) -- : Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/breisig.live/www/htdocs/libraries/src/Log/LogEntry.php on line 126

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/breisig.live/www/htdocs/libraries/vendor/symfony/error-handler/Error/OutOfMemoryError.php on line 1

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/breisig.live/www/htdocs/libraries/vendor/joomla/database/src/Monitor/DebugMonitor.php on line 77

Warning: PHP Request Shutdown: Cannot call session save handler in a recursive manner in Unknown on line 0

Hello,
i have currently big Problems after checkout: www.breisig.live/kasse/checkout/confirm

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/breisig.live/www/htdocs/libraries/src/Log/LogEntry.php on line 126

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/breisig.live/www/htdocs/libraries/vendor/symfony/error-handler/Error/OutOfMemoryError.php on line 1

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/breisig.live/www/htdocs/libraries/vendor/joomla/database/src/Monitor/DebugMonitor.php on line 77

Warning: PHP Request Shutdown: Cannot call session save handler in a recursive manner in Unknown on line 0

Can you please help me urgently ?
Thanks. Michael

Hi,

Seeing the number of results for the first filter (423) this can't be what is generating the problem. The mass action should only need a few dozen of MB maximum of memory, nowhere near the 1 GB limit.
So the error was generated by something else.
Do you have that error only once in the PHP error log ? Or several times ? What are the dates and times of the errors ? Recent ? Close or far appart in time ?

Do you have other mass actions ?
Could it be that someone regularly use the "export" button of the orders listing in the backend, without any filter and without selecting any order ? In that case, it would run a MySQL query loading all the data of all the orders at once, resulting in a similar issue.

It could also be a browser extension, or something between your browser and your server prefetching the export URL without you doing anything yourself :
- a CDN like cloudflare ( developers.cloudflare.com/speed/optimiza...ntent/prefetch-urls/ ) or keyCDN ( www.keycdn.com/support/prefetching ). Some potentially useful information regarding cloudFlare: serverfault.com/questions/1165854/503-re...h-requests-nginx-php
- a browser extension on your browser: chromewebstore.google.com/detail/quickli...ibilpmekhgkbeg?hl=en
- a setting of chrome on your computer: stackoverflow.com/questions/28020184/how...tch-in-google-chrome
- a prefetching joomla extension ( extensions.joomla.org/extension/page-speed-optimizer/ ) which would run in the backend while it shouldn't ( not saying this one does, but if you have an extension like that on your website, that's a thing to check ).

A good way to check if it comes from something triggering unwanted exports of orders is to add the line:
exit;
after the line:
function export(){
in the file administrator/components/com_hikashop/controllers/order.php
This way, the "export" button of the orders listing won't do anything on your website.
If you don't have the problem anymore after this change, then it would confirm that it comes from something triggering unwanted exports of orders on your website backend.

The database just stopped for a while again. It's difficult because I don't have all the data about the sql logs on the server.
This is all I have in joomla logs:
PHP ​​Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 56623120 bytes) in /public_html/administrator/components/com_hikashop/helpers/spreadsheet.php on line 192
PHP Warning: Undefined property: stdClass::$massaction_name in /public_html/plugins/actionlog/hikashop/hikashop.php on line 578
PHP Warning: Undefined property: stdClass::$massaction_name in /public_html/plugins/actionlog/hikashop/hikashop.php on line 589
PHP Warning: Undefined variable $customer_num_uses in /public_html/administrator/components/com_awocoupon/awocoupon/library/class-awocoupon-library-discount.php on line 5597

When checking database with query SHOW OPEN TABLES WHERE In_use > 0;
I get some lock tables.

Hi,

I think that there is a problem with your categories in your database.
You must have a loop something where a child category is a parent of one of its parent categories.

You can try to add the code:after the line:in the file administrator/components/com_hikashop/classes/category.php
That will avoid the infinite loop, and thus should not produce the error anymore if you click on the "rebuild" button of the categories listing.
Then, we can include the patch on our end too so that you can install the update without getting the error.
However, it still means that you have a problem with the data of your categories in the database. Ideally, you should review the child / parent structure of your categories to remove that infinite loop.