New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/34030#issuecomment-994893356

Comment:
sage-9.5.beta8_1 --massif
```
==26499== Massif, a heap profiler
==26499== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==26499== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==26499== Command: /usr/lib/sage-9.5.beta8/src/bin/sage-python -i
==26499== Parent PID: 26394
==26499==

valgrind: m_mallocfree.c:278 (mk_plain_bszB): Assertion 'bszB != 0' failed.
valgrind: This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.


host stacktrace:
==26499==    at 0x580F9061: ??? (in /usr/libexec/valgrind/massif-amd64-linux)
==26499==    by 0x580F90A7: ??? (in /usr/libexec/valgrind/massif-amd64-linux)
==26499==    by 0x580F9228: ??? (in /usr/libexec/valgrind/massif-amd64-linux)
==26499==    by 0x5813FCE4: ??? (in /usr/libexec/valgrind/massif-amd64-linux)
==26499==    by 0x581B772C: ??? (in /usr/libexec/valgrind/massif-amd64-linux)
==26499==    by 0x581B7CAB: ??? (in /usr/libexec/valgrind/massif-amd64-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 26499)
==26499==    at 0x48BE17B: free (in /usr/libexec/valgrind/vgpreload_massif-amd64-linux.so)
==26499==    by 0x11DF10: ??? (in /usr/bin/dash)
==26499==    by 0x10F445: ??? (in /usr/bin/dash)
==26499==    by 0x10E2B0: ??? (in /usr/bin/dash)
==26499==    by 0x115C0B: ??? (in /usr/bin/dash)
==26499==    by 0x10C6B2: ??? (in /usr/bin/dash)
==26499==    by 0x401E5E9: libc_start_main_stage2 (in /usr/lib/libc.so)
client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFEFFFB80
valgrind stack range: [0x100268E000 0x100278DFFF] top usage: 8896 of 1048576


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.
```