By running:
valgrind --leak-check=yes ./qemu-ppc tests/testthread
I can replicate a leak compared to qemu-arm with the same test....
==25789== at 0x483577F: malloc (vg_replace_malloc.c:299)
[13/7729]
==25789== by 0x4D7F8D0: g_malloc (in
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.3)
==25789== by 0x1FC65D: create_new_table (translate_init.inc.c:9252)
==25789== by 0x1FC65D: register_ind_in_table (translate_init.inc.c:9291)
==25789== by 0x1FC971: register_ind_insn (translate_init.inc.c:9325)
==25789== by 0x1FC971: register_insn (translate_init.inc.c:9390)
==25789== by 0x1FC971: create_ppc_opcodes (translate_init.inc.c:9450)
==25789== by 0x1FC971: ppc_cpu_realize (translate_init.inc.c:9819)
==25789== by 0x277263: device_set_realized (qdev.c:834)
==25789== by 0x27BBC6: property_set_bool (object.c:2076)
==25789== by 0x28019E: object_property_set_qobject (qom-qobject.c:26)
==25789== by 0x27DAF4: object_property_set_bool (object.c:1334)
==25789== by 0x27AE4B: cpu_create (cpu.c:62)
==25789== by 0x1C89B8: cpu_copy (main.c:188)
==25789== by 0x1CA44F: do_fork (syscall.c:5604)
==25789== by 0x1D665A: do_syscall1.isra.43 (syscall.c:9160)
==25789==
==25789== 6,656 bytes in 26 blocks are possibly lost in loss record 216 of 238
==25789== at 0x483577F: malloc (vg_replace_malloc.c:299)
==25789== by 0x4D7F8D0: g_malloc (in
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.3)
==25789== by 0x1FC65D: create_new_table (translate_init.inc.c:9252)
==25789== by 0x1FC65D: register_ind_in_table (translate_init.inc.c:9291)
==25789== by 0x1FC9BA: register_dblind_insn (translate_init.inc.c:9337)
==25789== by 0x1FC9BA: register_insn (translate_init.inc.c:9384)
==25789== by 0x1FC9BA: create_ppc_opcodes (translate_init.inc.c:9450)
==25789== by 0x1FC9BA: ppc_cpu_realize (translate_init.inc.c:9819)
==25789== by 0x277263: device_set_realized (qdev.c:834)
==25789== by 0x27BBC6: property_set_bool (object.c:2076)
==25789== by 0x28019E: object_property_set_qobject (qom-qobject.c:26)
==25789== by 0x27DAF4: object_property_set_bool (object.c:1334)
==25789== by 0x27AE4B: cpu_create (cpu.c:62)
==25789== by 0x17304D: main (main.c:681)
==25789==
==25789== 10,752 (1,024 direct, 9,728 indirect) bytes in 4 blocks are
definitely lost in loss record 223 of 238
==25789== at 0x483577F: malloc (vg_replace_malloc.c:299)
==25789== by 0x4D7F8D0: g_malloc (in
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.3)
==25789== by 0x1FC65D: create_new_table (translate_init.inc.c:9252)
==25789== by 0x1FC65D: register_ind_in_table (translate_init.inc.c:9291)
==25789== by 0x1FC998: register_dblind_insn (translate_init.inc.c:9332)
==25789== by 0x1FC998: register_insn (translate_init.inc.c:9384)
==25789== by 0x1FC998: create_ppc_opcodes (translate_init.inc.c:9450)
==25789== by 0x1FC998: ppc_cpu_realize (translate_init.inc.c:9819)
==25789== by 0x277263: device_set_realized (qdev.c:834)
==25789== by 0x27BBC6: property_set_bool (object.c:2076)
==25789== by 0x28019E: object_property_set_qobject (qom-qobject.c:26)
==25789== by 0x27DAF4: object_property_set_bool (object.c:1334)
==25789== by 0x27AE4B: cpu_create (cpu.c:62)
==25789== by 0x1C89B8: cpu_copy (main.c:188)
==25789== by 0x1CA44F: do_fork (syscall.c:5604)
==25789== by 0x1D665A: do_syscall1.isra.43 (syscall.c:9160)
So something funky happens to the PPC translator for each new thread....
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1836558
Title:
Qemu-ppc Memory leak creating threads
Status in QEMU:
Confirmed
Bug description:
When creating c++ threads (with c++ std::thread), the resulting binary
has memory leaks when running with qemu-ppc.
Eg the following c++ program, when compiled with gcc, consumes more
and more memory while running at qemu-ppc. (does not have memory leaks
when compiling for Intel, when running same binary on real powerpc CPU
hardware also no memory leaks).
(Note I used function getCurrentRSS to show available memory, see
https://stackoverflow.com/questions/669438/how-to-get-memory-usage-at-
runtime-using-c; calls commented out here)
Compiler: powerpc-linux-gnu-g++ (Debian 8.3.0-2) 8.3.0 (but same problem with
older g++ compilers even 4.9)
Os: Debian 10.0 ( Buster) (but same problem seen on Debian 9/stetch)
qemu: qemu-ppc version 3.1.50
---
#include <iostream>
#include <thread>
#include <chrono>
using namespace std::chrono_literals;
// Create/run and join a 100 threads.
void Fun100()
{
// auto b4 = getCurrentRSS();
// std::cout << getCurrentRSS() << std::endl;
for(int n = 0; n < 100; n++)
{
std::thread t([]
{
std::this_thread::sleep_for( 10ms );
});
// std::cout << n << ' ' << getCurrentRSS() << std::endl;
t.join();
}
std::this_thread::sleep_for( 500ms ); // to give OS some time to wipe
memory...
// auto after = getCurrentRSS();
std::cout << b4 << ' ' << after << std::endl;
}
int main(int, char **)
{
Fun100();
Fun100(); // memory used keeps increasing
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1836558/+subscriptions
