some part of code causes native heap corruption leading to usocket unable to resolve host
vityok opened this issue · 0 comments
vityok commented
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)