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.

Sign up for GitHub

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

Jump to bottom

some part of code causes native heap corruption leading to usocket unable to resolve host #92

Open
vityok opened this issue Mar 5, 2018 · 0 comments
Open

some part of code causes native heap corruption leading to usocket unable to resolve host #92

vityok opened this issue Mar 5, 2018 · 0 comments

Comments

@vityok
Copy link
Contributor

vityok commented Mar 5, 2018

Have witnessed this problem on Linux X86 and ARM32, SBCL and CCL: after doing several thousand HTTPS requests drakma stops resolving host name. Returning:

Name service error in "getaddrinfo": -11 (System error)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vityok