unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "J. Sims" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "63131@debbugs.gnu.org" <63131@debbugs.gnu.org>
Cc: "dev@jpoiret.xyz" <dev@jpoiret.xyz>
Subject: bug#63131: Dino explodes memory, CPU usage
Date: Thu, 27 Apr 2023 21:19:58 +0000	[thread overview]
Message-ID: <fuZG2xi33wcjVWr90dHINWS6tcLbtvzly02HfnsJAhBLMpmOJvbIcsf_czkuz44_HkS-IC_KAhbRXw60mBpRA3ldeL3CTHHL4x3A6_5He9Y=@protonmail.com> (raw)
In-Reply-To: <871qk5hy0p.fsf@jpoiret.xyz>

Hey,

------- Original Message -------
On Thursday, April 27th, 2023 at 16:26, Josselin Poiret <dev@jpoiret.xyz> wrote:


> Hi,
>
> I cannot reproduce on my end with a bare `guix shell dino -- dino`.
> What windowing system are you using? Does dino have logs? Have you
> tried launching it in a terminal to see if it outputs anything?

If dino has logs, I do not know where to find them; when launching from the terminal, a newline is emitted and absolutely nothing else before entering the described state. I am using GNOME.

Interestingly, your comment made me curious, so I ran a `guix shell --pure dino -- dino` to see what would happen. It launched fine, so I ran an update of the home profile (where I have it installed) and tried launching dino again - only to reproduce the same problem. I tried your command of `guix shell dino -- dino` - and got the same issue again. However, `guix shell --pure dino -- dino` still works fine. This leads me to believe the issues is another package in my home profile... but which?

I tested all of the packages in my home profile with dino in a pure shell, and it launched fine.

Okay, not packages. Environment variables? I changed some of those recently; let's try reverting them.

Nope, works fine.

The logical next consideration is services, but I'm not sure how to test those without... removing them, reconfiguring home, logging out, logging in... each and every time. It would be nice if you could pass eg `--preserve='^DISPLAY$'` to `guix home container`. Ah well. I'll do the hard thing anyway.

But before I go off to do that, I wanted to send this message with previous debug steps. Especially this interesting tidbit:

Firstly, I misspoke; Dino doesn't consume an entire thread and all the system's memory. It turns out gst-plugin-scanner consumes all the system's memory; the CPU seems to remain unabused.

With this information, I ran `dino --gst-debug-level=6` and found this interesting, repeating pattern:

```
0:00:27.310610920 31838      0x11d8520 LOG       GST_PLUGIN_LOADING gstpluginloader.c:1150:exchange_packets: Poll res = 0. 0 bytes pending for write
0:00:27.310655655 31838      0x11d8520 DEBUG               GST_POLL gstpoll.c:1241:gst_poll_fd_has_error: 0x13e81e0: fd (fd:25, idx:2) 0
0:00:27.310661435 31838      0x11d8520 DEBUG               GST_POLL gstpoll.c:1266:gst_poll_fd_can_read_unlocked: 0x13e81e0: fd (fd:25, idx:2) 0
0:00:27.310667858 31838      0x11d8520 DEBUG               GST_POLL gstpoll.c:1195:gst_poll_fd_has_closed: 0x13e81e0: fd (fd:25, idx:2) 0
0:00:27.310675101 31838      0x11d8520 DEBUG               GST_POLL gstpoll.c:1414:gst_poll_wait: 0x13e81e0: timeout :0:00:01.000000000
```

This appears to be the action upon which it locks up.

As I said, I'll go test if one of my home services is causing this issue; perhaps this information will be useful in the meantime.

Thanks,
Juli




  reply	other threads:[~2023-04-27 21:21 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 [this message]
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

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='fuZG2xi33wcjVWr90dHINWS6tcLbtvzly02HfnsJAhBLMpmOJvbIcsf_czkuz44_HkS-IC_KAhbRXw60mBpRA3ldeL3CTHHL4x3A6_5He9Y=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=63131@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).