similar to: Bug#767295: xl: apparent memory leak

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

On Thu, 2014-11-20 at 22:13 -0500, Gedalya wrote: > On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: > >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which > >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other > >> than the gzip one)

On Sat, 2014-11-08 at 08:32 -0500, Gedalya wrote: > On 11/08/2014 05:41 AM, Ian Campbell wrote: > > Please can you try running xl under valgrind, something similar to what > > I described earlier should work. > I guess it didn't find much.. Indeed not :-/ I managed to get a test box up and running, so I backported a couple of additional upstream patches to help valgrind

On 11/09/2014 07:02 AM, Ian Campbell wrote: > On Sat, 2014-11-08 at 08:32 -0500, Gedalya wrote: >> On 11/08/2014 05:41 AM, Ian Campbell wrote: >>> Please can you try running xl under valgrind, something similar to what >>> I described earlier should work. >> I guess it didn't find much.. > Indeed not :-/ > > I managed to get a test box up and running,

On 11/09/2014 07:18 AM, Gedalya wrote: > That memory block is just a bit larger than the size of the initrd in > the VM, could there be a connection? Nope. I changed the initrd to 2.6mb and that memory block is still exactly at 23852 / 14464 / 14464. Actually the process size is around 12 mb when pygrub is counting down to boot, then jumps up to 14+ mb

On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote: > When booting domU's running amd64 jessie, I notice some memory problems > with xl. I ran it (actually, upstream staging-4.4) under valgrind and it reported after a reboot: ==5722== 24 bytes in 1 blocks are definitely lost in loss record 35 of 72 ==5722== at 0x4026B2D: malloc (vg_replace_malloc.c:299) ==5722== by 0x41739FF:

On 11/08/2014 05:41 AM, Ian Campbell wrote: > Please can you try running xl under valgrind, something similar to what > I described earlier should work. I guess it didn't find much.. # valgrind --leak-check=full xl cr -F /etc/xen/auto/asterisk_deb80.cfg ==6736== Memcheck, a memory error detector ==6736== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==6736== Using

On Fri, 2014-11-07 at 21:32 -0500, Gedalya wrote: > On 11/06/2014 09:12 AM, Ian Campbell wrote: > > I've posted a fix for this upstream: > > http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html > > > > I've requested that it go into the next 4.4.x release. I also plan to > > backport it to the package regardless once it is accepted into the

reopen 767295 thanks The 4.4.1-4 release only included one related fix there are actually two more: commit 379b351889a8f02abe30a06e2ce9ba8b381b91ab Author: Ian Campbell <ian.campbell at citrix.com> Date: Thu Nov 6 13:00:31 2014 +0000 tools: libxl: do not leak diskpath during local disk attach

On Thu, 2014-11-06 at 12:14 +0000, Ian Campbell wrote: > On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote: > > When booting domU's running amd64 jessie, I notice some memory problems > > with xl. > > I ran it (actually, upstream staging-4.4) under valgrind and it reported > after a reboot: > > ==5722== 24 bytes in 1 blocks are definitely lost in loss record 35

On 11/06/2014 09:12 AM, Ian Campbell wrote: > I've posted a fix for this upstream: > http://lists.xen.org/archives/html/xen-devel/2014-11/msg00542.html > > I've requested that it go into the next 4.4.x release. I also plan to > backport it to the package regardless once it is accepted into the dev > branch. > > Ian. So I've tried building xen 4.4.1-3 with this

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

HI, I have 2 TDM400s plugged in a PC. I failed to use same channels to make a call to PSTN. It shows it can't establish connection after dial command issued. Below is the log. Actually, the call is established as I can hear voice from the called party but the softphone is still showing ringing. It seems the TDM card can't get an answered signal from PSTN. After 15 seconds, the call

Processing commands for control at bugs.debian.org: > severity 767295 important Bug #767295 [xen-utils-4.4] xl: apparent memory leak Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 767295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767295 Debian Bug Tracking System Contact owner at

On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: > http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about > various dynamic thresholds for growing and shrinking the heap. My guess > is that we are bouncing up and down over some threshold with every other > reboot. IOW I'm not overly concerned with this apparent bi-modality, so long as the amount isn't

I am trying to have the ring types different for internal and external incoming calls. I have followed the guide on the wiki, the SetVar executes, in extensions.conf I have it as s,1, Yet it doesn't work? When the phone rings, the ring type is the one I chose on the phone, it rings same tone for both when I test. Using Asterisk Stable. Anyone got this working and can

On Fri, 2014-11-21 at 15:25 -0500, Gedalya wrote: > On 11/21/2014 06:12 AM, Ian Campbell wrote: > > On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: > >> http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about > >> various dynamic thresholds for growing and shrinking the heap. My guess > >> is that we are bouncing up and down over some

On 11/21/2014 06:12 AM, Ian Campbell wrote: > On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: >> http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about >> various dynamic thresholds for growing and shrinking the heap. My guess >> is that we are bouncing up and down over some threshold with every other >> reboot. > IOW I'm not overly concerned

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

This looks more of a postfix than dovecot issue, the error is really odd though. Aki On 24.9.2019 22.51, Christopher Wooley via dovecot wrote: > I have been fighting with this for almost 2 days. I can't seem to get > the SMTP server to authenticate through SASL. I have turned so many > things off and on, I don't remember what I've done, anymore. Can > someone look at