From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "J. Sims" <jtsims@protonmail.com>, 63131-done@debbugs.gnu.org
Subject: bug#63131: Dino explodes memory, CPU usage
Date: Fri, 28 Apr 2023 09:46:07 +0200 [thread overview]
Message-ID: <87y1mch2kg.fsf@jpoiret.xyz> (raw)
In-Reply-To: <VT_0OH4v1E5VnNFlRj9aKtPz3zJh1nSzLhOggU_ymdDqscR1pyKybuQUqEV4Q9IJCikbCPvj6i5OOR300bc-A4Qr2tJikSl6WjdOE8kLh6E=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi,
"J. Sims" <jtsims@protonmail.com> writes:
> Problem resolved: apparently the issue was gst-plugins-bad in my system configuration causing problems (which I had hanging around from resolving a website-specific bug in GNOME Web... which I no longer daily-drive anyway).
>
> Thanks for sparking me to actually look into this.
Great to see it's resolved on your end!
> I don't know how to close bugs on debbugs or if this one can be considered resolved, so I'll leave that up to the discretion of more knowledgeable Guix hackers.
You can cc XXXX-done@debbugs.gnu.org instead of XXXX@debbugs.gnu.org
(just like this message), or send a control message to
control@debbugs.gnu.org.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
prev parent reply other threads:[~2023-04-28 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 20:04 bug#63131: Dino explodes memory, CPU usage J. Sims via Bug reports for GNU Guix
2023-04-27 20:26 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-27 21:19 ` J. Sims via Bug reports for GNU Guix
2023-04-27 21:35 ` J. Sims via Bug reports for GNU Guix
2023-04-28 7:46 ` Josselin Poiret via Bug reports for GNU Guix [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1mch2kg.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=63131-done@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jtsims@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).