-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Segmentation fault using https in multi-threaded environment #191
Comments
I got segmentation fault even when I had no |
Not reproducible on whateverable, which is even more interesting. FWIW another simple SEGV: rakudo/rakudo#1202 |
Also, FWIW, pretty much any segfault is a rakudobug. So please submit a rakudo ticket once there's more info (e.g. caught under gdb or golfed down significantly). |
Overriding get-connection, surrounding it with lock, and using my UserAgent2 instead of UserAgent seems to solve the problem. package HTTP {
our $https_lock = Lock.new;
class UserAgent2 is HTTP::UserAgent {
multi method get-connection(HTTP::Request $request, Str $host, Int $port?) {
{
$https_lock.lock;
LEAVE $https_lock.unlock;
return callsame;
}
}
}
} |
generates:
or just:
using HTTP is fine, so problem is somewhere in IO::Socket::SSL
my versions:
The text was updated successfully, but these errors were encountered: