GNU bug report logs - #63131
Dino explodes memory, CPU usage

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#63131: closed (Dino explodes memory, CPU usage)
Date: Fri, 28 Apr 2023 07:47:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 28 Apr 2023 09:46:07 +0200
with message-id <87y1mch2kg.fsf <at> jpoiret.xyz>
and subject line Re: bug#63131: Dino explodes memory, CPU usage
has caused the debbugs.gnu.org bug report #63131,
regarding Dino explodes memory, CPU usage
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
63131: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63131
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: "J. Sims" <jtsims <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: Dino explodes memory, CPU usage
Date: Thu, 27 Apr 2023 20:04:09 +0000

Hello,

As of at least commit bb385f247292d3162b27afa7ac48a1bf404c8e37, when attempting to launch Dino, it does not launch and instead consumes all system memory and 100% of a CPU thread's execution time.

Thanks,
Juli

[Message part 3 (message/rfc822, inline)]

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: "J. Sims" <jtsims <at> protonmail.com>, 63131-done <at> debbugs.gnu.org
Subject: Re: bug#63131: Dino explodes memory, CPU usage
Date: Fri, 28 Apr 2023 09:46:07 +0200

[Message part 4 (text/plain, inline)]

Hi,

"J. Sims" <jtsims <at> 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 <at> debbugs.gnu.org instead of XXXX <at> debbugs.gnu.org
(just like this message), or send a control message to
control <at> debbugs.gnu.org.

Best,
-- 
Josselin Poiret

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.