happened to me today, too.
i have a 1&1;Could Dynamic Server (http://www.1und1.info/xml/order/CloudDynamicServer) with 1GB Memory.
After putting some articles in a new shop today the site went offline.
/ and /admin are dead by now.
i set the memory limits in php.ini and .htaccess to 768 MB.
i can see the memory rise to 75% in “top” on my linux shell, when getting the shops index.php, and then the exception is throwed.
i just have 15 articles and 4 categories in my shop, how can this be?
why does the shop use so much memory?!?
this is imho a memory leak, isnt it?
anyways, is there a way to resolve this?
i dont want to go to another provider, this shop is already sold to a customer and we would really look silly if we tell them:"the server we chose for you does not meet the requirements” or “the shop system we chose is broken” -.-
we already purchased a theme für magento and our designer and another coder heavily customized it, so much money would be lost.
I have similar problem. In my customer’s store there are mainly configurable products. Checkout does not get further from the first step (billing) and I can see in the logs:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 523800 bytes) in /home/vhosts/*.*.*/htdocs/app/Mage.php on line 322, referer: http://*.*.*/checkout/onepage/
However it works with simple product! I’ve create a simple test product and it works fine with this.
Server is Apache 2.2 with 1GB memory (running on a VPS) with MySQL 5.1.41 and PHP 5.3.2
I don’t want to resurrect an old thread, but I was having this problem every time I went to the “manage downloads” page in the admin, using the MageWorx downloads module on a Windows Server.
The code attempts to return the download’s url from the actual file’s location, but uses the wrong file-directory delimiter ( ‘/’ ). So I modified the code to check the server’s OS and use ‘\\’ in the case of Windows. This solved the memory exception error.
The moral of the story is that the memory exception may not be due just because of memory limitations, but could be because of some faulty code somewhere.
I have a 1997 Ford Escort. The check engine light was on, and it started running bad. I took it in to a service center that specializes in Fords.
REI Coupon Code
The moral of the story is that the memory exception may not be due just because of memory limitations, but could be because of some faulty code somewhere.
I agree. The original post was concerning an old version of Magento, so anyone who stumbles on this now is probably experiencing a flaw in their own code.
For me, the flaw was a recursive PHP method I wrote. The method searches for a file within a directory or any sub-directories. At first, I was using scandir($directory), which adds ‘.’ and ‘..’ to the list or returned files/directories, so it ended up catching itself in an infinite loop of searching within itself and it’s parent directories, which used up all the memory. I swapped scandir() for glob(), and it worked fine.
I just got the same error from the cart and have narrowed down the problem.
I wrote an extension to handle adding items to the cart through ajax, and on a users first visit to the site, when they tried to add something to cart it would stall and return the memory error.
I took a look at my code and narrowed the problem down to this line:
So somewhere in the execution of the the line using the helper it ran into problems. The weird part is that it was only on a users first visit to the site, or more accurately, a user that had no cookies from the site. If I deleted my cookies I could recreate the error every time. But once I had run into the error and refreshed the page, everything worked fine, no conflicts no errors.
I figured I would share what I found and hope it helps someone running into the same problem.
