From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Alacritty is crashing rarely, but randomly
Date: Thu, 21 Jan 2021 18:46:05 +0100 [thread overview]
Message-ID: <20210121174605.L9ZMB2O3-bwxj_CBhmLdeBUbxq3RlA16HsHxTV2ZYbQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24521@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
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.
prev parent reply other threads:[~2021-01-21 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
2020-08-30 23:44 ` Alacritty is crashing rarely, but randomly ericonr
2020-09-01 5:53 ` tarkov2213
2020-09-01 5:56 ` tarkov2213
2020-09-01 5:57 ` tarkov2213
2020-09-01 5:58 ` tarkov2213
2020-09-01 5:59 ` tarkov2213
2020-09-25 11:39 ` svenper
2020-11-07 9:53 ` fosslinux
2020-11-07 12:48 ` ericonr
2020-11-07 13:09 ` tarkov2213
2021-01-21 17:46 ` ericonr
2021-01-21 17:46 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121174605.L9ZMB2O3-bwxj_CBhmLdeBUbxq3RlA16HsHxTV2ZYbQ@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).