We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
I using modsecurity v3.0.13 with nginx 1.26. After running one day, memory over to 90%. I using valgrind monitor memory. Below log of valgrind:
==300601== LEAK SUMMARY: ==300601== definitely lost: 1,024 bytes in 1 blocks ==300601== indirectly lost: 0 bytes in 0 blocks ==300601== possibly lost: 0 bytes in 0 blocks ==300601== still reachable: 21,007 bytes in 444 blocks ==300601== suppressed: 0 bytes in 0 blocks
Can you help me? Thanks
The text was updated successfully, but these errors were encountered:
Hi @nedngo,
I'm afraid there is not enough information to investigate this issue.
First, could you try (almost) the same configuration without ModSecurity?
Sorry, something went wrong.
No branches or pull requests
Describe the bug
I using modsecurity v3.0.13 with nginx 1.26. After running one day, memory over to 90%.
I using valgrind monitor memory. Below log of valgrind:
==300601== LEAK SUMMARY:
==300601== definitely lost: 1,024 bytes in 1 blocks
==300601== indirectly lost: 0 bytes in 0 blocks
==300601== possibly lost: 0 bytes in 0 blocks
==300601== still reachable: 21,007 bytes in 444 blocks
==300601== suppressed: 0 bytes in 0 blocks
Can you help me?
Thanks
The text was updated successfully, but these errors were encountered: