From: Fiona Ebner <f.ebner@proxmox.com>
To: Kefu Chai <k.chai@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH v2 pve-qemu 0/2] Re-enable tcmalloc as the memory allocator
Date: Tue, 14 Apr 2026 17:36:41 +0200 [thread overview]
Message-ID: <e2f32c37-30b8-47f3-bf93-d3e579417b09@proxmox.com> (raw)
In-Reply-To: <f626cf83-ea21-4412-946a-13469e799fa2@proxmox.com>
Am 14.04.26 um 1:08 PM schrieb Fiona Ebner:
> Note that I did play around with memory hotplug and ballooning before as
> well, not sure if related.
>
> Unfortunately, I don't have the debug symbols for librbd.so.1 right now:
>
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0 0x00007ea8da6442d0 in tc_memalign () from /lib/x86_64-linux-gnu/libtcmalloc.so.4
>> [Current thread is 1 (Thread 0x7ea8ca66a6c0 (LWP 109157))]
I had added malloc_stats(); calls around
MallocExtension_ReleaseFreeMemory(); to better see the effects, which
also requires including malloc.h in pve-backup.c when building for
tcmalloc. I also did a few backups before, so I can't rule out that it's
related to that. I did a build of librbd1 and librados2 with the debug
symbols now, but haven't been able to reproduce the issue yet. Will try
more tomorrow.
next prev parent reply other threads:[~2026-04-14 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 5:46 Kefu Chai
2026-04-14 5:46 ` [PATCH v2 pve-qemu 1/2] add patch to support using " Kefu Chai
2026-04-14 9:53 ` Fiona Ebner
2026-04-14 5:46 ` [PATCH v2 pve-qemu 2/2] d/rules: enable " Kefu Chai
2026-04-14 11:08 ` [PATCH v2 pve-qemu 0/2] Re-enable " Fiona Ebner
2026-04-14 15:36 ` Fiona Ebner [this message]
2026-04-15 10:22 ` Kefu Chai
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=e2f32c37-30b8-47f3-bf93-d3e579417b09@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=k.chai@proxmox.com \
--cc=pve-devel@lists.proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox