From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: latest Nvidia drivers cause system freeze on exit of Chromium or Electron-based programs
Date: Thu, 04 Nov 2021 18:01:29 +0100 [thread overview]
Message-ID: <20211104170129.4xRg5nU3lES2Eh2dgwNgc0ngX49YiFbymVrE5RmDvUQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32241@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/32241#issuecomment-961238263
Comment:
> It's a use-after-free. Nvidia should fix their shit. Leaving that bug in "because it doesn't always crash" is insane.
Do we look like nvidia employees? There is nothing we can do about it, there is no point in this issue being open.
next prev parent reply other threads:[~2021-11-04 17:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 6:47 [ISSUE] " seanlaguna
2021-07-29 7:51 ` seanlaguna
2021-07-29 10:23 ` ericonr
2021-07-29 19:02 ` Lolzen
2021-07-29 19:03 ` Lolzen
2021-07-29 20:54 ` abenson
2021-07-29 21:18 ` abenson
2021-07-30 10:06 ` reedts
2021-08-01 9:33 ` mvf
2021-08-01 13:09 ` reedts
2021-08-11 15:51 ` seankhl
2021-08-15 14:21 ` mvf
2021-08-19 6:58 ` RononDex
2021-08-20 10:57 ` annada-behera
2021-08-23 20:15 ` sloosch
2021-08-23 20:16 ` sloosch
2021-08-23 20:18 ` sloosch
2021-08-23 20:19 ` sloosch
2021-08-24 17:28 ` vikigenius
2021-08-25 18:42 ` Sogomn
2021-08-25 20:23 ` ericonr
2021-09-21 0:16 ` abenson
2021-09-29 11:07 ` RononDex
2021-11-02 18:02 ` mvf
2021-11-02 19:16 ` Duncaen
2021-11-02 19:16 ` Duncaen
2021-11-02 20:21 ` ericonr
2021-11-04 16:54 ` kiwec
2021-11-04 17:01 ` Duncaen [this message]
2021-11-04 17:09 ` kiwec
2021-11-04 17:13 ` Duncaen
2021-11-04 17:13 ` [ISSUE] [CLOSED] " Duncaen
2021-12-08 13:07 ` dm17
2022-02-09 6:57 ` seankhl
2022-02-09 7:13 ` vanessa-vd98
2022-02-09 17:18 ` RononDex
2022-02-10 7:14 ` kiwec
2022-02-10 8:46 ` seankhl
2022-08-11 11:34 ` kiwec
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=20211104170129.4xRg5nU3lES2Eh2dgwNgc0ngX49YiFbymVrE5RmDvUQ@z \
--to=duncaen@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).