From: Michael Brunnbauer <brunni@netestate.de>
To: libc-help@sourceware.org
Subject: Old Python binary eats all mem after upgrade to 2.28
Date: Wed, 08 Aug 2018 13:54:00 -0000 [thread overview]
Message-ID: <20180808135439.GA2177@netestate.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
hi all,
I just upgraded to glibc 2.28 and everything seems to run fine - except this
old binary of Python 2.1.3 from 2002 that came precompiled with Zope 2.6.0.
When I start it on the command line, it starts eating up all memory until
it gets killed by the oom-killer. strace looks like this:
mremap(0xe64aa000, 225259520, 225263616, MREMAP_MAYMOVE) = 0xe64aa000
mremap(0xe64aa000, 225263616, 225267712, MREMAP_MAYMOVE) = 0xe64aa000
mremap(0xe64aa000, 225267712, 225271808, MREMAP_MAYMOVE) = 0xe64aa000
mremap(0xe64aa000, 225271808, 225275904, MREMAP_MAYMOVE) = 0xe64aa000
mremap(0xe64aa000, 225275904, 225280000, MREMAP_MAYMOVE) = 0xe64aa000
mremap(0xe64aa000, 225280000, 225284096, MREMAP_MAYMOVE) = 0xe64aa000
...
I am in the very difficult process of moving away from that particular legacy
but this will take time. Also I'm concerned about other old binaries that may
stop working.
Any idea what is going on?
Regards,
Michael Brunnbauer
--
++ Michael Brunnbauer
++ netEstate GmbH
++ Geisenhausener Straße 11a
++ 81379 München
++ Tel +49 89 32 19 77 80
++ Fax +49 89 32 19 77 89
++ E-Mail brunni@netestate.de
++ https://www.netestate.de/
++
++ Sitz: München, HRB Nr.142452 (Handelsregister B München)
++ USt-IdNr. DE221033342
++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next reply other threads:[~2018-08-08 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:54 Michael Brunnbauer [this message]
2018-08-08 14:03 ` Michael Brunnbauer
2018-08-08 14:54 ` Florian Weimer
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=20180808135439.GA2177@netestate.de \
--to=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).