From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 65858@debbugs.gnu.org, guix-sysadmin <guix-sysadmin@gnu.org>
Subject: bug#65858: mumi crashes
Date: Mon, 09 Oct 2023 23:51:06 -0400 [thread overview]
Message-ID: <87y1gb5e51.fsf@gmail.com> (raw)
In-Reply-To: <874jizcsci.fsf@systemreboot.net> (Arun Isaac's message of "Tue, 10 Oct 2023 00:02:21 +0100")
Hi Arun,
Arun Isaac <arunisaac@systemreboot.net> writes:
> Hi Maxim,
>
> Thanks for monitoring mumi. I'm not sure why these mumi crashes are
> happening. I can think of two leads to start working on.
>
> 1. I see many lines such as those below that warn of garbage collection
> issues with "repeated allocations of large blocks". I am not sure, but
> this sounds like some limitation of the guile garbage collector. I
> suspect these warnings arise because the guile-email parser thrashes the
> garbage collector too much. I could look into rewriting parts of
> guile-email to be more careful with memory use.
>
> 2023-09-09 16:21:00 GC Warning: Repeated allocation of very large block (appr. size 16777216):
> 2023-09-09 16:21:00 May lead to memory leak and poor performance
> 2023-09-09 16:30:24 GC Warning: Repeated allocation of very large block (appr. size 16138240):
> 2023-09-09 16:30:24 May lead to memory leak and poor performance
> 2023-09-09 16:39:11 GC Warning: Repeated allocation of very large block (appr. size 16781312):
> 2023-09-09 16:39:11 May lead to memory leak and poor performance
Perhaps that could be related, but I have no such experience to
corroborate unfortunately.
> 2. If there is a specific query that causes mumi to crash, I'd like to
> find out. This could be a GraphQL query. Unfortunately the actual
> GraphQL document lives in the query part of the URI, and we don't log
> the query part. I can patch mumi to log the query part.
>
> WDYT?
I think adding more logging to narrow where the problem is happening
would be a fine action to take here!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-10 3:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 1:28 bug#65858: mumi crashes Maxim Cournoyer
2023-10-08 3:13 ` Maxim Cournoyer
2023-10-09 23:02 ` Arun Isaac
2023-10-10 3:51 ` Maxim Cournoyer [this message]
2023-10-10 22:57 ` Arun Isaac
2023-10-11 1:29 ` Maxim Cournoyer
2023-10-24 4:26 ` Maxim Cournoyer
2023-10-24 7:13 ` Christopher Baines
2023-10-24 12:47 ` Maxim Cournoyer
2023-10-24 13:15 ` Christopher Baines
2023-10-26 0:16 ` Arun Isaac
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=87y1gb5e51.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65858@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=guix-sysadmin@gnu.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.
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).