Skip to content
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

Accessing free'd request segfaults obviously #5

Closed
slact opened this issue Oct 18, 2009 · 2 comments
Closed

Accessing free'd request segfaults obviously #5

slact opened this issue Oct 18, 2009 · 2 comments

Comments

@slact
Copy link
Owner

slact commented Oct 18, 2009

When worker_processes > 1, there are occasional segfaults caused by trying to send a message (or in some way accessing) a listener's waiting request that has already been freed.

It is my understanding that when a request is completed (or aborted), the request's pool cleaner handlers will be called. Aborted requests are removed from a channel upon request pool cleanup, so it seems like the cleaner function is sometimes not called. Also, can't reproduce this with 1 worker process.

@slact
Copy link
Owner Author

slact commented Oct 19, 2009

Oh shit this is nontrivial. Worker process intercommunication is almost certainly necessary.
http://forum.nginx.org/read.php?2,14802

@slact
Copy link
Owner Author

slact commented Oct 22, 2009

done.

This issue was closed.
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

No branches or pull requests

1 participant