Summary of solutions to PHP has encountered an Access Violation problem

Summary of solutions to PHP has encountered an Access Violation problem_PHP tutorial

WBOY

Release： 2016-07-13 17:32:54

Original

1010 people have browsed it

This problem is not easy to handle, and it has confused many webmasters for a long time.
Mainly occurs on Windows hosting servers.
In php(as the current mainstream development language)official, http://bugs.php(as the current mainstream development language).net/
It is also possible to find two to three thousand pages of reports. Their officials are also at a loss. After 11 minor versions, they still have not completely solved it
http://bugs.php (as the current mainstream development language) .net/search.php(as the current mainstream development language)?cmd=display&search_for=php(as the current mainstream development language)+has+encountered+ an+access(favorite for small websites)&x=8&y=9

Currently, I will provide you with my maintenance experience in the past few years and some of my private solutions

First possibility:

Remove the eaccelerator extension in php(as the current mainstream development language)
This can solve your problem, but it may increase the burden on the system
Because eaccelerator is mainly to save money System resource stuff

The specific method is to find php(as the current mainstream development language).ini
If I help you configure it, it is usually in c:/php(as the current mainstream development language) Mainstream development language) /php (as the current mainstream development language) .ini or c:/winnt/php (as the current mainstream development language) .ini Or c:/windows/php(as the current mainstream development language).ini

Remove

zend_extension_ts="C:php(as the current mainstream development language)extensionseaccelerator_win_xxx.dll"
eaccelerator.shm_size="16"
eaccelerator.cache_dir="c: emp"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"

ea was mainly developed in a Unix environment, but the author ignored that windows actually does not have the memory sharing mechanism of the u host like the u host.
This bug has been submitted to them, hoping for 0.9 .5 can solve

Of course, if the problem with your machine is not serious, it is recommended to keep it. ea is a very excellent piece of php(as the current mainstream development language)Caching + acceleration software
Use it with zo , will reduce the system burden by about 50%-80%, and increase the load capacity, speed and efficiency by about 200%

The second possibility

session_save_path needs to set an actual physical path, and the directory needs all permissions of everyone, similar to 0777 of U host

The third possibility
c:/winnt/temp or c:/windows/temp
also requires all permissions of everyone, similar to 0777 of U host

The fourth possibility
Your memory is seriously insufficient. Check it. If there is a problem, please add more memory. It is best to add two memory at a time.
For example, add 1G of memory. It is best to add 2 Exactly the same 512M. Otherwise, the dual channel is not enabled and the effect is mediocre

The fifth possibility
The combination of ZendOptimizer and php(as the current mainstream development language)is not very good
Try another version
It is relatively stable at the moment The combination is
php(as the current mainstream development language)4.3.11+zo 2.5.10a
or php(as the current mainstream development language)4.4 .1+zo 3.0 beta2

The sixth possibility

This mostly belongs to users who use win2003
They have set restrictions in the application pool
For example, how long it takes to recycle, how much maximum memory is used, etc.
These settings will inevitably cause this classic php(As the current mainstream development language)Error
Wooden has been tested for hundreds of times, and we can guarantee that problems will appear here.