Ubuntu
qemu package

Memory tracing: glib/gmem.c: custom memory allocation vtable not supported

Bug #1491972 reported by TJ
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

15.10 Wily, amd64:

$ sudo kvm -drive file=/dev/sda,if=scsi -vga std

(process:3535): GLib-WARNING **: /build/glib2.0-3tdlHy/glib2.0-2.45.6/./glib/gmem.c:482: custom memory allocation vtable not supported

$ apt-cache policy qemu-kvm
qemu-kvm:
  Installed: 1:2.3+dfsg-5ubuntu4
  Candidate: 1:2.3+dfsg-5ubuntu4
  Version table:
 *** 1:2.3+dfsg-5ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qemu-kvm (Ubuntu):
status: New → Confirmed
Revision history for this message
derek (denc716) wrote :

@ubuntu-gnome:~$ kvm --version

(process:21080): GLib-WARNING **: /build/glib2.0-3tdlHy/glib2.0-2.45.6/./glib/gmem.c:482: custom memory allocation vtable not supported
QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu4), Copyright (c) 2003-2008 Fabrice Bellard

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hm, this comes from vl.c:2989 (in git) calling g_mem_set_vtable(&mem_trace), which has been around since 2011 to add tracepoints for g_malloc/g_free.

https://github.com/GNOME/glib/blob/master/glib/gmem.c shows that this function is deprecated.

This means that tracing won't work right, but should otherwise be innocuous. Will see what upstream thinks about it.

Changed in qemu-kvm (Ubuntu):
importance: Undecided → Low
summary: - glib/gmem.c: custom memory allocation vtable not supported
+ Memory tracing: glib/gmem.c: custom memory allocation vtable not
+ supported
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

(Note, fix for this was acked upstream)

Serge Hallyn (serge-hallyn)
affects: qemu-kvm (Ubuntu) → qemu (Ubuntu)
Changed in qemu (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
wangqiang.sheng (wangqiangsheng) wrote :

gmem.c:483: custom memory allocation vtable not supported

问题解决：
      yum –y install gperftools-libs

c) reboot system

[root@l23-4-22 154363a6-13e0-4570-a1ef-53f2becacfbd]# rpm -ql gperftools-libs
/usr/lib64/libprofiler.so.0
/usr/lib64/libprofiler.so.0.4.5
/usr/lib64/libtcmalloc.so.4
/usr/lib64/libtcmalloc.so.4.2.6
/usr/lib64/libtcmalloc_and_profiler.so.4
/usr/lib64/libtcmalloc_and_profiler.so.4.2.6
/usr/lib64/libtcmalloc_debug.so.4
/usr/lib64/libtcmalloc_debug.so.4.2.6
/usr/lib64/libtcmalloc_minimal.so.4
/usr/lib64/libtcmalloc_minimal.so.4.2.6
/usr/lib64/libtcmalloc_minimal_debug.so.4
/usr/lib64/libtcmalloc_minimal_debug.so.4.2.6

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Was that last update on a rather old qemu e..g in Trusty?
In any way a bit more info on the system in use would be nice and to not wake up this old bug too much if ok for you please create a new one with a reference to this one being mentioned.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.