與本徵+的std ::矢量+ OpenMP的

Question

內存泄漏我有徵是推動我瘋了的問題。每當我嘗試重新分配存儲在std :: vector中的一組Eigen :: MatrixXd時，我都會從valgrind獲取內存泄漏。

我已經重寫了我的代碼至少5次，我試過用std :: maps（這是我最初的解決方案的一部分），我已經從載體向量移動到純向量....沒有工作。只要我添加我的openMP指令，就會發生泄漏。

這裏有一個最小的工作示例：

#include <iostream> 
#include <Eigen/Dense> 
#include <vector> 
#include <omp.h> 

typedef Eigen::Matrix< float, Eigen::Dynamic, Eigen::Dynamic, Eigen::RowMajor > EMat; 

EMat function() { 
     EMat a(19,29); 
     return a; 
} 

int main() { 
     std::vector <EMat> v(10); 

#pragma omp parallel for schedule(dynamic) 
     for (unsigned int i = 0; i < 10; ++i) { 
       v[i] = function(); 
     } 
} 

如果我嘗試使用Valgrind的運行它，我得到：

r@darkstar ~/tmp $ valgrind --leak-check=full --show-leak-kinds=all ./test_leak==9640== Memcheck, a memory error detector 
==9640== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. 
==9640== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info 
==9640== Command: ./test_leak 
==9640== 
==9640== 
==9640== HEAP SUMMARY: 
==9640==  in use at exit: 4,632 bytes in 10 blocks 
==9640== total heap usage: 31 allocs, 21 frees, 48,952 bytes allocated 
==9640== 
==9640== 72 bytes in 1 blocks are still reachable in loss record 1 of 4 
==9640== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) 
==9640== by 0x4C2CF1F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) 
==9640== by 0x513F7F8: gomp_realloc (alloc.c:54) 
==9640== by 0x51439FA: gomp_team_start (team.c:376) 
==9640== by 0x51412E9: GOMP_parallel_loop_dynamic_start (loop.c:466) 
==9640== by 0x400EBD: main (test_leak.cpp:19) 
==9640== 
==9640== 192 bytes in 1 blocks are still reachable in loss record 2 of 4 
==9640== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) 
==9640== by 0x513F7A8: gomp_malloc (alloc.c:36) 
==9640== by 0x5143B8E: gomp_team_start (team.c:190) 
==9640== by 0x51412E9: GOMP_parallel_loop_dynamic_start (loop.c:466) 
==9640== by 0x400EBD: main (test_leak.cpp:19) 
==9640== 
==9640== 2,128 bytes in 7 blocks are possibly lost in loss record 3 of 4 
==9640== at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) 
==9640== by 0x4012E54: _dl_allocate_tls (dl-tls.c:296) 
==9640== by 0x5C33DA0: pthread_create@@GLIBC_2.2.5 (allocatestack.c:589) 
==9640== by 0x5143905: gomp_team_start (team.c:439) 
==9640== by 0x51412E9: GOMP_parallel_loop_dynamic_start (loop.c:466) 
==9640== by 0x400EBD: main (test_leak.cpp:19) 
==9640== 
==9640== 2,240 bytes in 1 blocks are still reachable in loss record 4 of 4 
==9640== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) 
==9640== by 0x513F7A8: gomp_malloc (alloc.c:36) 
==9640== by 0x51434D5: gomp_new_team (team.c:144) 
==9640== by 0x51405FC: gomp_parallel_loop_start (loop.c:447) 
==9640== by 0x51412E9: GOMP_parallel_loop_dynamic_start (loop.c:466) 
==9640== by 0x400EBD: main (test_leak.cpp:19) 
==9640== 
==9640== LEAK SUMMARY: 
==9640== definitely lost: 0 bytes in 0 blocks 
==9640== indirectly lost: 0 bytes in 0 blocks 
==9640==  possibly lost: 2,128 bytes in 7 blocks 
==9640== still reachable: 2,504 bytes in 3 blocks 
==9640==   suppressed: 0 bytes in 0 blocks 
==9640== 
==9640== For counts of detected and suppressed errors, rerun with: -v 
==9640== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) 

我搜索在網絡上花了很多時間和試驗，但沒有運氣。 任何人都可以幫助我嗎？

在此先感謝！

[R

Answer 1

這並不是因爲徵也不std::vector因爲OpenMP的的但是「泄露」或相當的valgrind報告不是「可信」。

如上所述，不要在此花費太多時間，您對這些泄漏不承擔任何責任。

見相關鏈接：

• does openmp allocate memory and free all after

至於我可以告訴libgomp不殺它催生了執行結束線程，使得內核清理做到這一點。

• gomp contains small memoryleak

在libgomp情況下，大部分的分配在退出時間仍可達 落入他們真的不能被釋放的範疇。