Agent RulesAgent Rules
SW

Swoole Memory Safety

Preventing memory leaks and state pollution in persistent workers

Swoole
Security
Use in BuilderAll Swoole Options

Details

Language / Topic
swooleSwoole
Category
Security

Rules

balanced
- Reset service containers between requests to avoid stale singletons leaking state.
- Monitor memory usage over time — use `memory_get_usage()` checks in long-running workers.
- Set `open_http_protocol`, `open_websocket_protocol` explicitly — disable unused protocols to reduce attack surface.
- Set `max_request` to auto-restart workers after N requests as a safety net against leaks.
- Never store user-specific data in class properties that persist across requests.