Title: Memory exhausted errors
Last modified: July 18, 2020

---

# Memory exhausted errors

 *  Resolved [FX Web Solutions](https://wordpress.org/support/users/fxwebsolutions/)
 * (@fxwebsolutions)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/memory-exhausted-errors/)
 * I tend to get a lot of 500 erros when Amelia is doing ajaxy things. My log file
   shows a lot of error messages like this:
 * `Allowed memory size of 100663296 bytes exhausted (tried to allocate 32768 bytes)
   in /srv/www/redacted.com/current/web/app/plugins/ameliabooking/src/Application/
   Commands/Booking/Appointment/GetAppointmentsCommandHandler.php on line 114`
 * Memory limit is set to 96M in php.ini and Amelia is the only plugin loaded.

Viewing 1 replies (of 1 total)

 *  Plugin Author [ameliabooking](https://wordpress.org/support/users/ameliabooking/)
 * (@ameliabooking)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/memory-exhausted-errors/#post-13146073)
 * Hi,
 * Thank you for contacting us.
 * It seems that you have small memory limit and that you need to expand it. Please
   contact your hosting provider for this.
 * Best regards.

Viewing 1 replies (of 1 total)

The topic ‘Memory exhausted errors’ is closed to new replies.

 * ![](https://ps.w.org/ameliabooking/assets/icon-256x256.png?rev=3429091)
 * [Booking for Appointments and Events Calendar - Amelia](https://wordpress.org/plugins/ameliabooking/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ameliabooking/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ameliabooking/)
 * [Active Topics](https://wordpress.org/support/plugin/ameliabooking/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ameliabooking/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ameliabooking/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [ameliabooking](https://wordpress.org/support/users/ameliabooking/)
 * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/memory-exhausted-errors/#post-13146073)
 * Status: resolved