I was also having the same problem, looked for phpinfo.ini, php.ini or .htaccess files to no avail. Finally I have looked at some php files, opened them and checked the codes inside for memory. Finally this solution was what I come out with and it worked for me. I was using wordpress, so this solution might only work for wordpress memory size limit problem. My solution, open default-constants.php file in /public_html/wp-includes folder. Open that file with code editor, and find memory settings under wp_initial_constants scope, or just Ctrl+F it to find the word "memory". There you will come over WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT. Just increase it, it was 64 MB in my case, I increased it to 128 MB and then to 200 MB.

// Define memory limits.
if ( ! defined( 'WP_MEMORY_LIMIT' ) ) {
    if ( false === wp_is_ini_value_changeable( 'memory_limit' ) ) {
        define( 'WP_MEMORY_LIMIT', $current_limit );
    } elseif ( is_multisite() ) {
        define( 'WP_MEMORY_LIMIT', '200M' );
    } else {
        define( 'WP_MEMORY_LIMIT', '128M' );
    }
}

if ( ! defined( 'WP_MAX_MEMORY_LIMIT' ) ) {
    if ( false === wp_is_ini_value_changeable( 'memory_limit' ) ) {
        define( 'WP_MAX_MEMORY_LIMIT', $current_limit );
    } elseif ( -1 === $current_limit_int || $current_limit_int > 268435456 /* = 256M */ ) {
        define( 'WP_MAX_MEMORY_LIMIT', $current_limit );
    } else {
        define( 'WP_MAX_MEMORY_LIMIT', '256M' );
    }
}

顺便说一句，请不要做下面的代码，因为这是不好的做法:

ini_set('memory_limit', '-1');

It is unfortunately easy to program in PHP in a way that consumes memory faster than you realise. Copying strings, arrays and objects instead of using references will do it, though PHP 5 is supposed to do this more automatically than in PHP 4. But dealing with your data set in entirety over several steps is also wasteful compared to processing the smallest logical unit at a time. The classic example is working with large resultsets from a database: most programmers fetch the entire resultset into an array and then loop over it one or more times with foreach(). It is much more memory efficient to use a while() loop to fetch and process one row at a time. The same thing applies to processing a file.

如果您的脚本需要分配这么大的内存，那么您可以通过在php文件中添加这一行来增加内存限制

ini_set('memory_limit', '44M');

其中，4400万是你预计消费的数量。

但是，大多数情况下，此错误消息意味着脚本正在做错误的事情，增加内存限制只会导致相同的错误消息，但数字不同。

因此，您必须重写代码，而不是增加内存限制，这样它就不会分配那么多内存。例如，在较小的块中处理大量数据，取消保存大值但不再需要的变量，等等。

我们也遇到过类似的情况，我们尝试了顶部给出的答案 报错(' memory_limit ', ' 1 '); 一切工作正常，压缩图像文件大于1MB到KBs。

COMPOSER_MEMORY_LIMIT=-1 composer require mageplaza/module-core

这里有两个简单的方法来增加共享主机的限制:

如果您可以访问PHP.ini文件，请更改PHP.ini中的行 如果你的线显示为32M，试试64M: memory_limit = 64M;一个脚本可能消耗的最大内存(64MB) 如果你不能访问PHP.ini，试着把这个添加到。htaccess文件中: php_value memory_limit 64M