I tried to install FrontEndUser under Module Manager, but it shows the following error,
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 349639 bytes) in /mounted-storage/home39c/sub001/sc30583-IOFH/idugai.com/modules/nuSOAP/classes/nusoap.php on line 6219
How to rectify this???
Fatal error: Allowed memory size of 33554432 bytes exhausted
-
- New Member
- Posts: 6
- Joined: Wed Aug 17, 2011 5:58 am
Re: Fatal error: Allowed memory size of 33554432 bytes exhau
I get that as well on some hosts and never found a workaround, besides adding modules the old fashioned way.
Re: Fatal error: Allowed memory size of 33554432 bytes exhau
Increase the PHP Memory limit in the config.php
- + - + - + - + - + - + -
LATEST TUTORIAL AT CMS CAN BE SIMPLE:
Migrating Company Directory module to LISE
Migrating Company Directory module to LISE
- + - + - + - + - + - + -
Re: Fatal error: Allowed memory size of 33554432 bytes exhau
To me, the message doesn't make sense... It tries to allocate 350K, but it ran out of it's allowed 34MFatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 349639 bytes)

Re: Fatal error: Allowed memory size of 33554432 bytes exhau
Hi Wayne
Hope you are well. It could be because the overall memory is being used by other processes.
For some modules it is better to install by downloading the xml file and using that as there are a number of modules CGExtensions to name just one which I can never get to install via the module manager.
Hope you are well. It could be because the overall memory is being used by other processes.
For some modules it is better to install by downloading the xml file and using that as there are a number of modules CGExtensions to name just one which I can never get to install via the module manager.
Re: Fatal error: Allowed memory size of 33554432 bytes exhau
I can never install CGExtensions using the XML.. I always get an "XML Corrupted" message.
I found out that if a developer re-releases a version of a module, you will always get a checksum error when using the module manager.
I found out that if a developer re-releases a version of a module, you will always get a checksum error when using the module manager.
Re: Fatal error: Allowed memory size of 33554432 bytes exhau
This is very strange... The forum says I posted this today... I posted this in August.Wishbone wrote:To me, the message doesn't make sense... It tries to allocate 350K, but it ran out of it's allowed 34MFatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 349639 bytes)

Re: Fatal error: Allowed memory size of 33554432 bytes exhau
Odd behaviour indeed....
Btw, 2 things on the subject. ModuleManager has some changes inside, which will be in 1.10 and should make the installing more stable there.
Second, the 350K it tries to allocate are the alllocated memory for that mentioned module. In total you have 32M, which should be fine for a clean install, but when installing multiple additional modules, I would increase to 48M or 64M. So the message is that CMSMS is loaded and other modules as well, but that the last chunk that is tried to be allocated for the mentioned module is making it cross the memory_limit.
You could increase memory_limit in the php.ini, if you have access. Otherwise the .htaccess or the config.php are alternatives, but they will only work if your hoster allows overriding the server settings.
Ronny
Btw, 2 things on the subject. ModuleManager has some changes inside, which will be in 1.10 and should make the installing more stable there.
Second, the 350K it tries to allocate are the alllocated memory for that mentioned module. In total you have 32M, which should be fine for a clean install, but when installing multiple additional modules, I would increase to 48M or 64M. So the message is that CMSMS is loaded and other modules as well, but that the last chunk that is tried to be allocated for the mentioned module is making it cross the memory_limit.
You could increase memory_limit in the php.ini, if you have access. Otherwise the .htaccess or the config.php are alternatives, but they will only work if your hoster allows overriding the server settings.
Ronny