On Sun, 2014-04-20 at 13:23 +0100, Nicholas Clark wrote: > On Sun, Apr 20, 2014 at 12:41:13PM +0200, Philippe Waroquiers wrote: > > It looks like gcc20 is thrashing. > > Looks to be because of one valgrind memcheck process > > user 'nick' > > using about 24 GB (21GB resident). > > > > If that is not expected, it would be good to kill it. > > Otherwise, I will be patient :). > > I'm sorry about this. Laurent Guerby has already killed it, which was the > right > thing to do. > > I'd forgotten that this was still running (I was waiting for it, hoping that > it would finish), but I wasn't aware that it was chewing RAM, particularly to > the point that it was making the machine unusable for everyone. > > I'll be more careful in the future. In particular, I'll figure out how to > ulimit them so that it kills them before they grow excessively large. Ok, thanks (that was no big problem :).
BTW, if you upgrade to a recent (SVN) Valgrind version, you can get some more information about what Valgrind is doing using the vgdb command v.info stats Maybe might help to understand why it had so much memory. Philippe _______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
