search for: 171c6d7ac17e

Displaying 4 results from an estimated 4 matches for "171c6d7ac17e".

2014 Nov 09
2
Bug#767295: Bug#767295: Bug#767295: xl: apparent memory leak
...[ anon ] with each reboot. The size seems to be the same each time. I can't quite figure out what this new mapping is. I'll keep digging. [...] > > Could you also post your guest cfg file please. > Thanks, nothing unusual here but worth confirming. Ian. [0] b1dfc531d8ad and 171c6d7ac17e, FWIW
2014 Nov 09
0
Bug#767295: Bug#767295: Bug#767295: xl: apparent memory leak
...ueeze or wheezy VMs. That memory block is just a bit larger than the size of the initrd in the VM, could there be a connection? > >>> Could you also post your guest cfg file please. > Thanks, nothing unusual here but worth confirming. > > Ian. > > [0] b1dfc531d8ad and 171c6d7ac17e, FWIW >
2014 Nov 08
0
Bug#767295: Bug#767295: Bug#767295: xl: apparent memory leak
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
2014 Nov 08
2
Bug#767295: Bug#767295: Bug#767295: xl: apparent memory leak
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