Skip to content

Fixed config and memory leakage #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 28, 2013

Conversation

chaizhenhua
Copy link
Contributor

No description provided.

brenosilva added a commit that referenced this pull request Mar 28, 2013
Fixed config and memory leakage
@brenosilva brenosilva merged commit 9b1d6bf into owasp-modsecurity:remotes/trunk Mar 28, 2013
@chaizhenhua chaizhenhua deleted the Bugfix branch March 28, 2013 02:31
@brenosilva
Copy link
Contributor

Hello chaizhenhua,

Applied. However it did not fix the ngx_pool_context issue. The nginx module only works well if i comment the ngx_pool_context code inside ngx_http_modsecurity.c

@chaizhenhua
Copy link
Contributor Author

the “ModSecurityEnabled” unknown issue? or something else ?

@brenosilva
Copy link
Contributor

Nginx module is crashing when i send a request with ngx_pool_context:

2013/03/26 14:44:03 [notice] 25580#0: signal 17 (SIGCHLD) received
2013/03/26 14:44:03 [alert] 25580#0: worker process 25592 exited on signal 11
2013/03/26 14:44:03 [notice] 25580#0: start worker process 25598
2013/03/26 14:44:03 [notice] 25580#0: signal 29 (SIGIO) received

If i disable ngx_pool_context module, it works.
Any idea ?

Thanks

@brenosilva
Copy link
Contributor

Hello man,

Please i noticed this issue: #60
I think it could be related to the change between apr_pstr* to ngx_pstr* ?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants