search for: freememori

Dear all, I have wrapped a C++ function in an R package. I allocate/deallocate memory using C++ 'new' and 'delete'. In order to allow user interrupts without memory leaks I've moved all the delete statements required after an interrupt to a separate C++ function freeMemory(), which is called using on.exit() just before the .C() call. I am concerned about the

Hello, Thank you for your reply. I am missing an intermediate step as > plot( strptime( Time, format = "%H:%M:%S"), FreeMemory) Error in strptime(Time, format = "%H:%M:%S") : invalid `x' argument > plot( strptime( c(Time), format = "%H:%M:%S"), FreeMemory) Error in strptime(c(Time), format = "%H:%M:%S") : invalid `x' argument

Hi all, I am running KVM on a 3.18 kernel. The system runs and Atom processor with 2Gb RAM. Using KVM you obviously can over allocate your resources: say you have 4 guests each configured with 1GB ram. Running all four at the same time, depending on the workload, can crash the system - I get a kernel trace when this happens. But let's consider a simpler case: one guest with 1.5 Gb RAM,

The following is an example of a dataframe containing times, plus some numeric data. foo <- c("12:39:26","12:40:22","12:41:19") bar <- data.frame(foo,1:3,11:13) Note that the times are of class 'factor' (their class changes in this case, as they go into the dataframe). To convert this dataframe to an 'its', do the following: library(its)

On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 12:30, Andrei Perietanu wrote: > > Hi all, > > > > I am running KVM on a 3.18 kernel. The system runs and Atom processor > with > > 2Gb RAM. > > > > Using KVM you obviously can over allocate your resources: say you have 4 > > guests each configured

On Tue, Jan 26, 2016 at 1:51 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 14:35, Andrei Perietanu wrote: > > On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> > > wrote: > > > >> On 26.01.2016 12:30, Andrei Perietanu wrote: > >>> Hi all, > >>> > >>> I am running KVM on a 3.18

On 26.01.2016 12:30, Andrei Perietanu wrote: > Hi all, > > I am running KVM on a 3.18 kernel. The system runs and Atom processor with > 2Gb RAM. > > Using KVM you obviously can over allocate your resources: say you have 4 > guests each configured with 1GB ram. Running all four at the same time, > depending on the workload, can crash the system - I get a kernel trace when

On 26.01.2016 14:35, Andrei Perietanu wrote: > On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> > wrote: > >> On 26.01.2016 12:30, Andrei Perietanu wrote: >>> Hi all, >>> >>> I am running KVM on a 3.18 kernel. The system runs and Atom processor >> with >>> 2Gb RAM. >>> >>> Using KVM you

I run this prog (http://www.compcar.ru/forum/showthread.php?t=7342)and this error appears: Fatal error occurred in main thread. Address:0x004a1f11 Exception:0xc0000005 I added every library whitch Igo needed (native-builtin) / I found them by Ollydebuger in Windows 7/ , but no success :( Could I add some other info to solve this?

As planned the new release is available at: ftp://libvirt.org/libvirt/ It is a rather large release with near 400 commits included. From an user point of view the main improvement is likely to be when using migration as various work has been done to extend the protocol and to avoid having the migration command stop other concurrent operations (like virsh list). See below for a number of