* [ISSUE] Alacritty is crashing randomly
@ 2020-08-28 0:28 ericonr
2020-08-30 23:44 ` Alacritty is crashing rarely, but randomly ericonr
` (11 more replies)
0 siblings, 12 replies; 13+ messages in thread
From: ericonr @ 2020-08-28 0:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
New 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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
@ 2020-08-30 23:44 ` ericonr
2020-09-01 5:53 ` tarkov2213
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ericonr @ 2020-08-30 23:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-683486986
Comment:
New dmesg: `[756383.268185] traps: alacritty[10149] trap invalid opcode ip:5620875805de sp:7fff38656930 error:0 in alacritty[56208726c000+3d5000]`
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
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
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-09-01 5:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-684384486
Comment:
Perhaps related, I have had this issue and an even more egregious variant where entire applications launched from alacritty would disappear.
On Fedora 31 Gnome Wayland. Optimus laptop with zram constantly being utilized. Discrete GPU was turned off in bios at the time.
Solution was to turn on the discrete GPU and use Nouveau. I suspect that for whatever reason the Intel GPU <-> system memory interaction was handled more poorly than with Nouveau somehow mediating it. The switch solved other graphical problems when memory was being full too (stuttering sound in videos + kernel cpu utilization through the roof), which ironically was what I wanted to avoid by turning off the discrete GPU to begin with.
Alacritty uses graphics elements which probably makes it subject to GPU memory constraints in some way.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
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
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-09-01 5:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-684384486
Comment:
Perhaps related, I have had this issue and an even more egregious variant where entire applications launched from alacritty would disappear.
On Fedora 31 Gnome Wayland. Optimus laptop with zram constantly being utilized. Discrete GPU was turned off in bios at the time.
Solution was to turn on the discrete GPU and use Nouveau. I suspect that for whatever reason the Intel GPU <-> system memory interaction was handled more poorly than with Nouveau somehow mediating it. The switch solved other graphical problems when memory was being full too (stuttering sound in videos + kernel cpu utilization through the roof), which ironically was what I wanted to avoid by turning off the discrete GPU to begin with.
As far as I can tell the GPU is never even used (optimus power button light indicator), yet the problem is solved.
Alacritty uses graphics elements which probably makes it subject to GPU memory constraints in some way.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (2 preceding siblings ...)
2020-09-01 5:56 ` tarkov2213
@ 2020-09-01 5:57 ` tarkov2213
2020-09-01 5:58 ` tarkov2213
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-09-01 5:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-684384486
Comment:
Perhaps related, I have had this issue and an even more egregious variant where entire applications launched from alacritty would disappear.
On Fedora 31 Gnome Wayland. Optimus laptop with zram constantly being utilized. Discrete GPU was turned off in bios at the time.
Solution was to turn on the discrete GPU and use Nouveau. I suspect that for whatever reason the Intel GPU <-> system memory interaction was handled more poorly than with Nouveau somehow mediating it. The switch solved other graphical problems when memory was being full too (stuttering sound in videos + kernel cpu utilization through the roof), which ironically was what I wanted to avoid by turning off the discrete GPU to begin with.
As far as I can tell the dGPU is never even used (optimus power button light indicator), yet the problem is solved.
Alacritty uses graphics elements which probably makes it subject to GPU memory constraints in some way.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (3 preceding siblings ...)
2020-09-01 5:57 ` tarkov2213
@ 2020-09-01 5:58 ` tarkov2213
2020-09-01 5:59 ` tarkov2213
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-09-01 5:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-684384486
Comment:
Perhaps related, I have had this issue and an even more egregious variant where entire applications launched from alacritty would disappear.
On Fedora 31 Gnome Wayland. Optimus laptop with zram constantly being utilized. Discrete GPU was turned off in bios at the time.
Solution was to turn on the discrete GPU and use Nouveau. I suspect that for whatever reason the Intel GPU <-> system memory interaction was handled more poorly than with Nouveau somehow mediating it. The switch solved other graphical problems when memory was being full too (stuttering sound in videos + kernel cpu utilization through the roof), which ironically was what I wanted to avoid by turning off the discrete GPU to begin with.
As far as I can tell the dGPU is never even used (optimus power button light indicator), yet the problem is solved.
Alacritty uses graphics elements (I recall being unable to even run it on some very old hardware because of opengl version or something) which probably makes it subject to GPU memory constraints in some way.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (4 preceding siblings ...)
2020-09-01 5:58 ` tarkov2213
@ 2020-09-01 5:59 ` tarkov2213
2020-09-25 11:39 ` svenper
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-09-01 5:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-684384486
Comment:
Perhaps related, I have had this issue and an even more egregious variant where entire applications launched from alacritty would disappear.
On Fedora 31 Gnome Wayland. Optimus laptop with zram constantly being utilized. Discrete GPU was turned off in bios at the time.
Solution was to turn on the discrete GPU and use Nouveau. I suspect that for whatever reason the Intel GPU <-> system memory interaction was handled more poorly than with Nouveau somehow mediating it. The switch solved other graphical problems when memory was being full too (stuttering sound in videos + kernel cpu utilization through the roof), which ironically was what I wanted to avoid by turning off the discrete GPU to begin with.
As far as I can tell the dGPU is never even used (optimus power button light indicator), yet the problem is solved.
Alacritty uses gpu api (I recall being unable to even run it on some very old hardware because of opengl version or something) which probably makes it subject to GPU memory constraints in some way.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (5 preceding siblings ...)
2020-09-01 5:59 ` tarkov2213
@ 2020-09-25 11:39 ` svenper
2020-11-07 9:53 ` fosslinux
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: svenper @ 2020-09-25 11:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
New comment by svenper on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-698881594
Comment:
I have had no problems like this with alacritty on bspwm, on a computer with only Intel internal graphics.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (6 preceding siblings ...)
2020-09-25 11:39 ` svenper
@ 2020-11-07 9:53 ` fosslinux
2020-11-07 12:48 ` ericonr
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: fosslinux @ 2020-11-07 9:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-723425196
Comment:
I do not have this issue on i915 alacritty on GNOME Xorg no dGPU, or on nvidia340/noveadu alacritty on i3. I am using glibc on both systesms.
@ericonr @svenper @tarkov2213 Do you use musl? This opcode stuff looks muslish.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (7 preceding siblings ...)
2020-11-07 9:53 ` fosslinux
@ 2020-11-07 12:48 ` ericonr
2020-11-07 13:09 ` tarkov2213
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ericonr @ 2020-11-07 12:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-723442239
Comment:
Yeah, Musl. Do you think it could be blowing past the per thread stack, perhaps?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (8 preceding siblings ...)
2020-11-07 12:48 ` ericonr
@ 2020-11-07 13:09 ` tarkov2213
2021-01-21 17:46 ` ericonr
2021-01-21 17:46 ` [ISSUE] [CLOSED] " ericonr
11 siblings, 0 replies; 13+ messages in thread
From: tarkov2213 @ 2020-11-07 13:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
New comment by tarkov2213 on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-723444358
Comment:
The Fedora system I had this exact issue happen to wasn't musl. But I found a fix, zram with vm.watermark_scale_factor=800
Never happened again. Might be an issue with some graphics API usage and how it handles low vram situations?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (9 preceding siblings ...)
2020-11-07 13:09 ` tarkov2213
@ 2021-01-21 17:46 ` ericonr
2021-01-21 17:46 ` [ISSUE] [CLOSED] " ericonr
11 siblings, 0 replies; 13+ messages in thread
From: ericonr @ 2021-01-21 17:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/24521#issuecomment-764823270
Comment:
There isn't really anything to act on, and I haven't experienced it for some time.
@tarkov2213 interestingly I have also recently enabled zram
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [ISSUE] [CLOSED] Alacritty is crashing rarely, but randomly
2020-08-28 0:28 [ISSUE] Alacritty is crashing randomly ericonr
` (10 preceding siblings ...)
2021-01-21 17:46 ` ericonr
@ 2021-01-21 17:46 ` ericonr
11 siblings, 0 replies; 13+ messages in thread
From: ericonr @ 2021-01-21 17:46 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2021-01-21 17:46 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` [ISSUE] [CLOSED] " ericonr
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).