Title: Error memory
Last modified: September 1, 2016

---

# Error memory

 *  Resolved [almendron](https://wordpress.org/support/users/almendron/)
 * (@almendron)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/)
 *     ```
       Fatal error: Allowed memory size of 947912704 bytes exhausted (tried to allocate 540813374 bytes) in C:\wamp64\www\revista\installer.php on line 1476
       Call Stack
       #	Time	Memory	Function	Location
       1	0.0000	1192720	{main}( )	...\installer.php:0
       2	11.8750	542039464	file_put_contents ( )	...\installer.php:1476
       ```
   
 * 1.- Server local (wampserver 64).
    2.- Size file SQL : 515M 3.- PHP.INI
 *     ```
       post_max_size 1000M
       upload_max_filesize 900M
       max_execution_time 5000
       max_input_time 5000
       memory_limit 1000M
       ```
   
 * 4.- phpmyadmin.conf
 *     ```
       php_admin_value upload_max_filesize 900M
       php_admin_value post_max_size 1000M
       php_admin_value max_execution_time 5000
       php_admin_value max_input_time 5000
       php_admin_value memory_limit 1000M
       ```
   
 * but the error persists
 * [https://wordpress.org/plugins/duplicator/](https://wordpress.org/plugins/duplicator/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * (@corylamleorg)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561188)
 * Hi almendron,
 * I have seen that issue once before, but its with really large DB files. Right
   now the routine uses file_put_contents, but there are some other techniques we
   might be able to use to work with larger databases. I have added this item to
   our work queue to look into improving.
 * In the meantime you may have to up your values a bit more, I would double them,
   I have found that the memory_limit setting doesn’t always correlate I believe
   the amount that it shows you in tried to allocate xxxx bytes is the amount over
   and above the memory limit in PHP. Also another process you can try is before
   you build the DB is run a plugin like [wp-optimize](https://wordpress.org/plugins/wp-optimize/).
 * Cheers~
 *  Thread Starter [almendron](https://wordpress.org/support/users/almendron/)
 * (@almendron)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561201)
 * 1.- Wampserver: change version of PHP from 5.6.19 to 7.0.4
    2.- Default values
   PHP.INI: memory_limit (128M), post_max_size (8M), upload_max_filesize (2M),….
   3. phpmyadmin.conf:
 *     ```
       php_admin_value upload_max_filesize 700M
       php_admin_value post_max_size 750M
       php_admin_value max_execution_time 5000
       php_admin_value max_input_time -1
       ```
   
 * **And all perfect** except an error
 *     ```
       **ERROR** database error write ‘Incorrect string value: ‘\xF0\x9F\x98\x89″ …’ for ...., pero esto es debido a problemas con el juego de caracteres.
       ```
   
 * Solution: edit file “my.ini” and add to the section [mysqld] the following line:
 *     ```
       sql_mode = NO_ENGINE_SUBSTITUTION
       ```
   
 * Finally .. I guess there will be an explanation and I guess not so much related
   to the values of PHP.INI as the “file_put_contents” command.
 *  [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * (@corylamleorg)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561209)
 * The NO_ENGINE_SUBSTITUTION fix we haven’t really found a way to at this point
   to fix via code, but the other issue you had with the size problem we believe
   we may be able to enhance some to not require as much memory… Thanks for posting
   your solution and reading the other threads…
 *  Thread Starter [almendron](https://wordpress.org/support/users/almendron/)
 * (@almendron)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561213)
 * I’m happy to help,
    regards
 *  [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * (@corylamleorg)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561253)
 * Closing down topic thread…
 * Cheer~

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Error memory’ is closed to new replies.

 * ![](https://ps.w.org/duplicator/assets/icon-256x256.png?rev=2906985)
 * [Duplicator - Backups & Migration Plugin - Cloud Backups, Scheduled Backups, & More](https://wordpress.org/plugins/duplicator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/duplicator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/duplicator/)
 * [Active Topics](https://wordpress.org/support/plugin/duplicator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/duplicator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/duplicator/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/error-memory-2/#post-7561253)
 * Status: resolved