Allowed memory size exhausted while upgrading

63 Posts

Thalion Reply #1, 17 years, 2 months ago

Hi !

I have a problem while trying to upgrade my installation to the latest SVN (5627) from a previous one (don’t remember the number, it was between Beta 1 and Beta 2)

When I launch the install process after the summary, I get after a while :

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 10104 bytes) in D:\xampplite\htdocs\online\core\xpdo\om\xpdoobject.class.php on line 39

It should be noted that the line number changes, as well as the "tried to allocate" amount.

I had emptied the cache folder as well as the session table before launching the process.

While building the SVN I noticed the following error (happens every time I build it, even after loading it again from scratch)

[2009-08-07 23:03:19] (INFO) Default workspace packaged.
[2009-08-07 23:03:26] (ERROR) Error preparing statement for query: SELECT `modTransportProvider`.`id` AS `modTransportProvider_id`, `modTransportProvider`.`name ` AS `modTransportProvider_name`, `modTransportProvider`.`description` AS `modTransportProvider_description`, `modTransportProvider`.`service_url` AS `modTransportProvider_service_url`, `modTransportProvider`.`created` AS `modTransportProvider_created`, `modTransportProvider`.`updated` AS `modTransportProvider_updated` FROM `modx_transport_providers` AS `modTransportProvider` WHERE `modTransportProvider`.`service_url` = ? OR `modTransportProvider`.`service_url` = ?
[2009-08-07 23:03:26] (INFO) Packaged in modxcms.com provisioner reference.

My environment is :
Xampp 1.6.8 under Windows XP
php 5.2.6
Memory_limit = 32M
max_execution_time = 240
Apache 2.2.9
MySQL 5.0.67

Is this a problem with this version of SVN, should I wait a next one ? Or is it a problem with my config ? Or my actual installation ?
How can I solve this ?

Thanks

4,149 Posts

splittingred Reply #2, 17 years, 2 months ago

Set your memory_limit in your php.ini to 128M.

shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com

63 Posts

Thalion Reply #3, 17 years, 2 months ago

Ok, this works alright, but I still have a problem with this : my host is set at 32M, and I cannot change it.
So even though I test everything locally on Xampp, I would have this problem again when I try to upgrade my live website ?

Plus, it seems strange to me that the setup checks for a 32M availability, but actually requires more ? Maybe this is something that is not really looked into until the official release ? (I understand that doing such a nice piece of works requires to look at plenty of things, with some more important than others)

4,149 Posts

splittingred Reply #4, 17 years, 2 months ago

Quote from: Thalion at Aug 07, 2009, 05:10 PM

Ok, this works alright, but I still have a problem with this : my host is set at 32M, and I cannot change it.
So even though I test everything locally on Xampp, I would have this problem again when I try to upgrade my live website ?

You can’t change it? Could you file a ticket asking? PHP 5.3.0 ships out with the memory_limit at 128M...

Plus, it seems strange to me that the setup checks for a 32M availability, but actually requires more ? Maybe this is something that is not really looked into until the official release ? (I understand that doing such a nice piece of works requires to look at plenty of things, with some more important than others)

Well, there are a lot of factors that go into the install process’s eventual runtime speed, and speed tests locally have done it in 27M or less; so theoretically the lowest required setting is 32M. But we might recommend users to up it to 128M.

However, we also are planning some install improvements to speed up the install process. To give you some background information, the reason it takes so much memory is the PclZip extension that Revo uses for its transport packages - including core.transport.zip, which is the main install file.

Also, are you installing the traditional or advanced packages? If you’re having memory limit usage issues and using the advanced, try the traditional.

shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com

63 Posts

Thalion Reply #5, 17 years, 2 months ago

I finally solved it by adding at the start of the setup/index.php file the following line :
@ini_set(’memory_limit’,’128M’);

and it did work without any problem, either locally or on my hosting server.

Thanks for pointing me the right direction, Shaun !