From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer] gui: remove G_SLICE=always-malloc usage
Date: Thu, 7 Aug 2025 14:29:14 +0200 [thread overview]
Message-ID: <175456679358.13117.16836384664068398728.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250807095420.210040-1-m.sandoval@proxmox.com>
On Thu, 07 Aug 2025 11:54:12 +0200, Maximiliano Sandoval wrote:
> Since Glib 2.76 there is no need to set this environment variable as
> this is the default now. For more details see the release notes of
> 2.75.3 (pre-release for 2.76). Additionally, when run under Valgrind it
> would use malloc even from before 2.75.3.
>
> Proxmox VE 9 ships with libglib2.0 2.84.
>
> [...]
Applied, thanks!
[1/1] gui: remove G_SLICE=always-malloc usage
commit: 4aa4db2997b213c498acae2598252ca488f19ae8
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-07 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 9:54 [pve-devel] " Maximiliano Sandoval
2025-08-07 12:29 ` Thomas Lamprecht [this message]
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=175456679358.13117.16836384664068398728.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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