awc causing SIGSEGV on Alpine

## Expected Behavior

The creation of the new awc client should work as it does on Ubuntu or there should be an error.

## Current Behavior

The first time an awc client is created, the program stops without any error. After the program is restarted and again creates an Awc client, it stops with error code 139 (SIGSEGV). I suspect that the first error is also a SEIGSEGV but it's catched by someone.
Docker output (the second `Finished dev` is after the container is restarted by docker):
```
app_1 | Finished dev [unoptimized + debuginfo] target(s) in 1m 38s
app_1 | Running `target/debug/awc-test`
app_1 | [2023-04-01T08:50:34Z INFO actix_server::builder] starting 4 workers
app_1 | [2023-04-01T08:50:34Z INFO actix_server::server] Actix runtime found; starting in Actix runtime
app_1 | [2023-04-01T08:50:59Z DEBUG awc_test] creating client
app_1 | Finished dev [unoptimized + debuginfo] target(s) in 0.09s
app_1 | Running `target/debug/awc-test`
app_1 | [2023-04-01T08:51:00Z INFO actix_server::builder] starting 4 workers
app_1 | [2023-04-01T08:51:00Z INFO actix_server::server] Actix runtime found; starting in Actix runtime
app_1 | [2023-04-01T08:51:03Z DEBUG awc_test] creating client
awc-test_app_1 exited with code 139
```

## Steps to Reproduce

1. Download example code: [awc-alpine-sigsegv.zip](https://github.com/actix/actix-web/files/11128949/awc-alpine-sigsegv.zip)
2. Run `docker-compose up`

## Context

I am trying to write a program that receives logs via post requests and stores them in a database. Specific events should be reported using discord webhooks.

## Your Environment

The code is compiled and executed inside an Alpine docker container.

- Rust version: `rustc 1.68.2 (9eb3afe9e 2023-03-27)`
- Gcc version: `12.2.1 20220924 (Alpine 12.2.1_git20220924-r4)`
- Actix Web version: 4.3.1
- Awc version: 3.1.1
- Alpine docker image version: 3.17

## Edit

It looks like this is an issue with the `openssl` feature. When using the `rustls` feature instead everything is working as expected. Maybe this is an openssl issue and not an awc one?