c ++程序中进程的内存使用情况

时间:2016-11-29 10:11:23

标签: c++ memory-management memory-leaks hashmap emplace

在我的C ++程序中,我使用

* m_Map= new map<int, list<object> >();
delete(m_Map);
m_Map->erase(TxId);

我添加了1000000个元素来映射,我在循环中不时检查进程的内存使用情况

for(int x=1;x<=1000000;x++){
    m_Map->emplace(txId, OBject);
    if(x%100000==0) {
        process_mem_usage(vm, rss);
        cout << "after add a key  VM: " << vm << "; RSS: " << rss << endl;
        }
    }

然后我再次通过从地图中删除逐个元素来打印RSS内存使用过程

 for(int x=1;x<=1000000;x++){
      m_Map->erase(x);
      if(x%100000==0) {
           process_mem_usage(vm, rss);
           cout << "after earse a key VM: " << vm << "; RSS: " << rss << endl;
        }
 }

使用此内存使用功能

void process_mem_usage(double& vm_usage, double& resident_set)
{
   using std::ios_base;
   using std::ifstream;
   using std::string;

   vm_usage     = 0.0;
   resident_set = 0.0;

   // 'file' stat seems to give the most reliable results
   //
   ifstream stat_stream("/proc/self/stat",ios_base::in);

   // dummy vars for leading entries in stat that we don't care about
   //
   string pid, comm, state, ppid, pgrp, session, tty_nr;
   string tpgid, flags, minflt, cminflt, majflt, cmajflt;
   string utime, stime, cutime, cstime, priority, nice;
   string O, itrealvalue, starttime;

   // the two fields we want
   //
   unsigned long vsize;
   long rss;

   stat_stream >> pid >> comm >> state >> ppid >> pgrp >> session >> tty_nr
               >> tpgid >> flags >> minflt >> cminflt >> majflt >> cmajflt
               >> utime >> stime >> cutime >> cstime >> priority >> nice
               >> O >> itrealvalue >> starttime >> vsize >> rss; // don't care about the rest

   stat_stream.close();

   long page_size_kb = sysconf(_SC_PAGE_SIZE) / 1024; // in case x86-64 is configured to use 2MB pages
   vm_usage     = vsize / 1024.0;
   resident_set = rss * page_size_kb;
}

我想出了这个我无法理解的结果。

 Initially VM: 12660; RSS: 1120
after add a key  VM: 28240; RSS: 16960
after add a key  VM: 43816; RSS: 32536
after add a key  VM: 59524; RSS: 48112
after add a key  VM: 75100; RSS: 63688
after add a key  VM: 90676; RSS: 79264
after add a key  VM: 106384; RSS: 95104
after add a key  VM: 121960; RSS: 110680
after add a key  VM: 137672; RSS: 126256
after add a key  VM: 153248; RSS: 141832
after add a key  VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408
after earse a key VM: 168824; RSS: 157408


after destroying the map VM: 12672; RSS: 1536

我觉得当我从地图中删除键,值对时应该释放内存。但是你可以看到它不会释放内存,直到我最后删除(免费)地图

delete(m_Map);

有人可以解释它是如何在c ++中发生的,我看了一下c ++ map :: emplace,erase function documentation.which没有给出任何关于此的线索..

1 个答案:

答案 0 :(得分:0)

您可以认为进程有两个不同的内存分配器。 当您从内核请求内存时,会使用第一个分配器(sbrk(2)mmap(2))。 第二个是使用空间分配器,它将从第一个分配器获得的内存分割为来自C ++代码的请求。

执行new / malloc时 - 请求第二个内存分配器(如果内存无法满足您的请求,可以使用第一个分配器从内核请求更多内存)。当你执行delete / free时 - 你将内存放弃到第二个分配器,它可以(但不是必须!)将内存返回给第一个分配器和内核。

所以它没有必要意味着,当你newmalloc / deletefree时,它会立即导致{{1}的更改}或RSS