All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110714] Xorg crashes randomly because of memory leak
Date: Fri, 06 Sep 2019 16:17:42 +0000	[thread overview]
Message-ID: <bug-110714-8800-OkiPNK8Tpi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110714-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 656 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110714

--- Comment #19 from John Lindgren <john-ytntcHzVV1kcWVvVuXF20w@public.gmane.org> ---
I just saw this same crash (Xorg 1.20.4 here still though).  I also had
Firefox, VirtualBox, Evolution, and a few smaller applications running.  The
computer had been running for most of the week already, so maybe a memory leak
somewhere?

My card is:

01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M]
(rev a2)

I am using xf86-video-modesetting.  Should I be using xf86-video-nouveau
instead?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1424 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-09-06 16:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  8:38 [Bug 110714] New: Xorg crashes randomly because of memory leak bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110714-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-05-20 10:03   ` [Bug 110714] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-20 11:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-20 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  6:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  6:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  7:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03 12:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-04 10:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-05 12:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-11 17:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12  5:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12  8:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12 11:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12 12:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 22:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-06 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-09-06 16:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-06 16:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-07 14:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-07 14:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-110714-8800-OkiPNK8Tpi@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.