Web Technician OnlineWhat does this mean?
Memory exhaustion happens when a PHP request reaches its configured allocation limit. A blank page or critical error does not prove that this is the cause; a log entry such as an allowed-memory-size error is better evidence. Higher limits can hide an inefficient task and increase total server pressure.
What should I check first?
Read the host’s PHP log at the exact time of the failed action. Record the requested operation, configured memory setting and recent changes. Check whether the failure appears only during a large import, image operation or particular plugin workflow.
How can I diagnose the cause?
Compare the hosting plan’s supported PHP limits with the application’s reported values. WordPress settings cannot necessarily override a server-level restriction. Inspect whether a plugin repeatedly loads large data or an unusually large image caused the allocation to grow.
How do I fix it safely?
Save configuration before editing and test on staging. Reduce the workload or repair the identified plugin issue where possible. Increase memory only within the host’s documented limits and confirm which configuration mechanism it supports; do not add contradictory settings to multiple files.
Verify the fix and know when to contact your provider
Retest the specific action and monitor resource use. If the effective limit does not change or exhaustion continues, send the host the error line, current values and workload description. Remove temporary public debugging and retain a rollback copy. Avoid posting log entries that contain personal data or credentials.
Work through these checks in order
- Look for a memory-exhaustion error at the failed request time and note the component or action. A generic critical-error message without this evidence does not justify raising memory.
- Compare the effective PHP limit in Site Health or the host panel with the plan’s allowed configuration. Ask the host which setting can actually control it before adding values to wp-config.php.
- Retest a smaller version of the workload and the normal workload after a targeted change. If usage grows unexpectedly again, investigate the plugin or task rather than repeatedly increasing the allocation.
Which tool can help?
DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.