From: Florian Weimer <fweimer@redhat.com>
To: Michael Brunnbauer <brunni@netestate.de>, libc-help@sourceware.org
Subject: Re: Old Python binary eats all mem after upgrade to 2.28
Date: Wed, 08 Aug 2018 14:54:00 -0000 [thread overview]
Message-ID: <0021a68e-80ab-31fd-1869-941dfca35a10@redhat.com> (raw)
In-Reply-To: <20180808140305.GA2306@netestate.de>
On 08/08/2018 04:03 PM, Michael Brunnbauer wrote:
> I should have provided more strace-context. This is what happens shortly
> before the endless mremap starts:
>
> stat64("/home/zope/2.6.0/lib/python2.1/site-packages", {st_mode=S_IFDIR|0775, st_size=304, ...}) = 0
> openat(AT_FDCWD, "/home/zope/2.6.0/lib/python2.1/site-packages", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 4
> fstat64(4, {st_mode=S_IFDIR|0775, st_size=304, ...}) = 0
> brk(0x812c000) = 0x812c000
> getdents(4, /* 10 entries */, 32768) = 244
> mmap2(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf73e2000
> mremap(0xf73e2000, 135168, 139264, MREMAP_MAYMOVE) = 0xf73c0000
> ...
Could you attach gdb and see which glibc function, if any, is called
here? Is there code from a Python extension module on the call stack?
Thanks,
Florian
next prev parent reply other threads:[~2018-08-08 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:54 Michael Brunnbauer
2018-08-08 14:03 ` Michael Brunnbauer
2018-08-08 14:54 ` Florian Weimer [this message]
2018-08-08 20:23 ` Michael Brunnbauer
2018-08-09 6:27 ` Florian Weimer
2018-08-09 7:32 ` Michael Brunnbauer
2018-08-09 8:39 ` Florian Weimer
2018-08-09 9:21 ` Florian Weimer
2018-08-09 10:47 ` Michael Brunnbauer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0021a68e-80ab-31fd-1869-941dfca35a10@redhat.com \
--to=fweimer@redhat.com \
--cc=brunni@netestate.de \
--cc=libc-help@sourceware.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.
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).