php扩展中c++单例模式的全局对象实例被生成多个子进程销毁,为啥?该如何解决
php扩展中c++单例模式的全局对象实例被生成多个子进程销毁,为啥??
在php扩展中是用了一个单例模式的全局对象,当http服务停止时通过日志查看并且打印进程号,发现析构函数被多次调用,并且是在不同的进程里(通过进程号观察)。 为什么会这样! 不是说http服务启动一次 ,我那全局对象就实例化一次吗! 服务停止时怎么会发生这么多怪异的现象!
------解决方案--------------------
请问你如何知道析构函数被多次调用?另外是不是你在程序里有被实例化多次?
------解决方案--------------------
是谁在响应 HTTP 请求?apache、IIS ...
PHP 在 HTTP 请求中的地位?web 服务器的应用程序
所以对于每一个与 PHP 相关的 HTTP 请求,都会触发一个 PHP 进(线)程
你的扩展是以动态链接库存在的,在进(线)程中是独立的
如果你想使你扩展的类被各进(线)程共享,就必须修改php的内核,不过无论是在什么系统中,这个内核都不是开源的,都是以库方式提供的
------解决方案--------------------
你php是cgi跑的吧,那的确会不停的构造与析构,因为都是每次都是新的Php解释器进程加载一堆动态库,其中包括你那个静态的C++对象,每个PHP进程加载同一份动态库,但它们内存是隔离的。
楼主用fcgi跑php的话就不一样了,只有在并发请求数超过当前的fcgi进程数情况下才会创建新的fcgi进程,不过也肯定不是多进程共享的。
------解决方案--------------------

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











What’s still popular is the ease of use, flexibility and a strong ecosystem. 1) Ease of use and simple syntax make it the first choice for beginners. 2) Closely integrated with web development, excellent interaction with HTTP requests and database. 3) The huge ecosystem provides a wealth of tools and libraries. 4) Active community and open source nature adapts them to new needs and technology trends.

IIS and PHP are compatible and are implemented through FastCGI. 1.IIS forwards the .php file request to the FastCGI module through the configuration file. 2. The FastCGI module starts the PHP process to process requests to improve performance and stability. 3. In actual applications, you need to pay attention to configuration details, error debugging and performance optimization.

Multiple calls to session_start() will result in warning messages and possible data overwrites. 1) PHP will issue a warning, prompting that the session has been started. 2) It may cause unexpected overwriting of session data. 3) Use session_status() to check the session status to avoid repeated calls.

NGINX and Apache each have their own advantages and disadvantages, and the choice should be based on specific needs. 1.NGINX is suitable for high concurrency scenarios because of its asynchronous non-blocking architecture. 2. Apache is suitable for low-concurrency scenarios that require complex configurations, because of its modular design.

Laravel optimizes the web development process including: 1. Use the routing system to manage the URL structure; 2. Use the Blade template engine to simplify view development; 3. Handle time-consuming tasks through queues; 4. Use EloquentORM to simplify database operations; 5. Follow best practices to improve code quality and maintainability.

AI can help optimize the use of Composer. Specific methods include: 1. Dependency management optimization: AI analyzes dependencies, recommends the best version combination, and reduces conflicts. 2. Automated code generation: AI generates composer.json files that conform to best practices. 3. Improve code quality: AI detects potential problems, provides optimization suggestions, and improves code quality. These methods are implemented through machine learning and natural language processing technologies to help developers improve efficiency and code quality.

Apache remains important in today's technology ecosystem. 1) In the fields of web services and big data processing, ApacheHTTPServer, Kafka and Hadoop are still the first choice. 2) In the future, we need to pay attention to cloud nativeization, performance optimization and ecosystem simplification to maintain competitiveness.

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.
