Bug#1041836: libc6 2.36-9+deb12u1 double free abort

To: Aurelien Jarno <aurel32@debian.org>, 1041836@bugs.debian.org
Subject: Bug#1041836: libc6 2.36-9+deb12u1 double free abort
From: Paul Szabo <paul.szabo@sydney.edu.au>
Date: Thu, 10 Aug 2023 16:46:20 +1000
Message-id: <[🔎] 277a3914-37e1-eb30-4208-5003cabfbecd@sydney.edu.au>
Reply-to: Paul Szabo <paul.szabo@sydney.edu.au>, 1041836@bugs.debian.org
In-reply-to: <[🔎] eb6aa80e-3039-d1ad-e961-e5bb221fc10b@sydney.edu.au>
References: <169017315036.10181.711257644926784572.reportbug@charlie.y.n> <[🔎] c37fde56-1030-4819-b59d-0ce30e92c647@sydney.edu.au> <[🔎] ZNQEJOmjhHfRpCdR@aurel32.net> <[🔎] eb6aa80e-3039-d1ad-e961-e5bb221fc10b@sydney.edu.au> <169017315036.10181.711257644926784572.reportbug@charlie.y.n>

I now tried the idea whether the amount of memory in the machine has a
relevance to my "inetd: double free detected in tcache 2, abort" issue.
I tried "mem=8G" and similar as kernel boot parameter; that produced
more-or-less the expected results for memory shown by "free", but did
not help to fix the issue. I may try to change physical RAM modules,
not sure whether have suitable replacements.

Cheers, Paul
-- 
Paul Szabo       psz@maths.usyd.edu.au       www.maths.usyd.edu.au/u/psz
School of Mathematics and Statistics   University of Sydney    Australia

Reply to:

Follow-Ups:
- Bug#1041836: libc6 2.36-9+deb12u1 double free abort
  - From: Aurelien Jarno <aurel32@debian.org>

References:
- Bug#1041836: libc6 2.36-9+deb12u1 double free abort
  - From: Paul Szabo <paul.szabo@sydney.edu.au>
- Bug#1041836: libc6 2.36-9+deb12u1 double free abort
  - From: Aurelien Jarno <aurel32@debian.org>
- Bug#1041836: libc6 2.36-9+deb12u1 double free abort
  - From: Paul Szabo <paul.szabo@sydney.edu.au>

Prev by Date: Bug#1041836: root unable to write un-owned
Next by Date: Bug#1041836: libc6 2.36-9+deb12u1 double free abort
Previous by thread: Bug#1041836: root unable to write un-owned
Next by thread: Bug#1041836: libc6 2.36-9+deb12u1 double free abort
Index(es):
- Date
- Thread