Closed issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24521

Description:
### System

* xuname:  
  Void 5.8.3_1 x86_64-musl GenuineIntel notuptodate rrnDDFFFFFFFFFFFFFFFFFFFFFFFFFFFF
* package:  
  alacritty-0.5.0_1

### Expected behavior

It will stay open indefinitely.

### Actual behavior

It crashes randomly, usually when I'm away from the device. I come back and the workspace occupied by alacritty is now empty. I managed to grab a core file and it doesn't have too much info, but notes that there was a `SIGILL` that killed the process.

dmesg:

```
[499358.471354] traps: alacritty[3578] trap invalid opcode ip:55f400fb15de sp:7ffff9af63b0 error:0 in alacritty[55f400c9d000+3d5000]
```

Interestingly enough, another alacritty instance just disappeared, without leaving complaints in dmesg or a core file. This is usually what happens.

### Steps to reproduce the behavior

- run alacritty in sway
- use i915 driver, if that matters
- use fish terminal, if that matters

I'm opening this issue here first because we do patch stuff around the relevant toolchains, but I will also look into upstream.