Third-party module causes fatal error memory exhausted (increasing memory limit does not help)

[Vitazzz]

I'm trying to use a custom carrier module which includes dynamic pricing and uses one of regular shipment options as a base, but I did not manage to make it work. Even when I increase memory limit up to 1024m it still causes an error, just showing different size of memory. The funniest part is that the module designers were not able to solve anything. They said that their module is designed and configured properly and the problem is on "my side" (they said script problem or something), but did not explain any further. So what could be the guilty part? Maybe the server configuration? Or some Presta files? Is it possible to find it?

Edited February 14, 2015 by Vitazzz (see edit history)

[bellini13]

this would usually indicate one of 2 things

 

1) there is a memory leak somewhere.  the process is either in some repeatable loop that slowly consumes all available memory until it hits the limit.  increasing the memory limit doesn't help, as the process will just continue to run until hitting the new limit.  Or there is really just some bug in the software that is being used that has a memory leak. 

 

2) the process just requires a massive amount of memory

 

I am not familiar with the module or what it has to accomplish, but using 1GB of memory leads me to believe #1.

 

What you first need to determine is where exactly does the memory get used.  Does it always happen at the same point (is it during checkout, during module configuration, during order creation etc...).  If you can figure out exactly when the issue occurs, and if it is always at the same point, then the module developer should be helping to determine what is executing at that point in time.  It could very well be unexpected issue occurring, they certainly should not rule out their module until exploring it more (unless they have already done this).