From: tarkov2213 <tarkov2213@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Alacritty is crashing rarely, but randomly
Date: Tue, 01 Sep 2020 07:59:57 +0200 [thread overview]
Message-ID: <20200901055957.ye1gdKn-mYqKPVJH9LQDxXH1kakAUiKInIw8Q-juVh0@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: 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.
next prev parent reply other threads:[~2020-09-01 5:59 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 [this message]
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
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=20200901055957.ye1gdKn-mYqKPVJH9LQDxXH1kakAUiKInIw8Q-juVh0@z \
--to=tarkov2213@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).