bug#63131: closed (Dino explodes memory, CPU usage)

[GNU bug Tracking System]

Your message dated Fri, 28 Apr 2023 09:46:07 +0200
with message-id <87y1mch2kg.fsf@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@gnu.org.)


-- 
63131: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63131
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> 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
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#63131: Dino explodes memory, CPU usage Date: Fri, 28 Apr 2023 09:46:07 +0200

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

signature.asc
Description: PGP signature

--- End Message ---