Message d'erreur comparaison produits

Bonjour,
Sur le site www.portes-eden.fr/ , lorsqu'on essaie de comparer des produits, on a parfois une page blanche avec le message d’erreur suivant :
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25190865 bytes) in XXXX/libraries/joomla/cache/storage/file.php on line 142.
En vidant les caches, le problème se règle, mais nous sommes obligé de surveiller toutes les semaines que le problème ne revient pas.
Dans la configuration de joomla, le cache progressif est activé et la durée du cache est réglée sur 5000
Est-ce un problème que vous avez déjà identifié avec Hikashop? Pourriez-vous me donner une piste quant à l'origine du problème?
Merci.

Bonjour retour,

Do you read English? Good. Because I don't write French, sorry.

Did you fixed it already? Your site is accessible...

If not:

Search "allowed memory size" here on the forum or elsewhere, and you'll get plenty of hints towards the fact that your system is long running out of just this: memory. The memory limit, which is currently strangling you, is typically set in a so-called php.ini file on your (host's) server. If your host let's you access the file... we don't know. Many hosts don't allow their users this. Best contact him.

The reason? Something in your website demands that much memory, obviously. Like so often in life, it adds up from many little things, but one big fat file needing to be processed can speed such things dramatically up. Must not be HikaShop, at least not alone. And hardly the program itself, but more likely something that it's 'working with'.

Anyway, you need a good chunk more memory. Take everything your host is willing to give you. Not sure if you'll get it, but 256M would be really nice, hehe. Add your numbers up and come out with way more than half of that already. 128M is sure not enough...

Good luck!

Ok. If it's not Hikashop I'm going to check if there is another component which can be responsible of that.

Thanks.

Again, it can be anything, or a combination of things. You should contact your host, if somehow possible (might be necessary anyway to get to the php.ini and rid of the memory bottleneck), or check tools you might have in your user panel on the host server - there might be an app able to help you finding the main performance hog(s) and memory gobbler(s).