memory leak -- a bad one

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Here is a top-except from corosync 2.3.4 running for under 15 hours:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
15406 root      20   0 10.5g 9.2g 9168 S  2.0 58.8  11:50.07 corosync

(I'm using fixed-width font in gmail;I have no idea what happens to this text when going via pipermail)

It's showing a RES usage of 9.2 GB. This high memory usage is after a relatively minor configuration change -- moving the listed nodes from totem.interface.member{ } to  nodelist.node { }. Two nodes were also added. AFAIK this was the only change. 

A review of changes since 2.3.4 indicates this has not been fixed since that release.


--
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss

[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux