释放由C语言中的malloc(),realloc()分配的所有内存

时间:2016-07-13 16:22:06

标签: c memory memory-management memory-leaks valgrind

我试图通过malloc(),realloc()来释放()所有已分配的内存,但是valgrind说这是内存泄漏。

代码:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>


int main(int argc, char *argv[]) {

    int lines_allocated = 128;
    int max_line_len = 50;

    FILE *fp;

    /* File allocate lines of text */
    char **array = (char **)malloc(sizeof(char*)*lines_allocated);
    if (array==NULL) {
        fprintf(stderr,"Out of memory (1).\n");
        exit(1);
    }

    FILE *file = fopen("file.txt", "r");
    if (file == NULL) {
        fprintf(stderr,"Error opening file.\n");
        exit(2);
    }

    int il;
    for (il = 0; 1; il++) {
        int j;

        /* Have we gone over our line allocation? */
        if (il >= lines_allocated) {
            int new_size;

            /* Double our allocation and re-allocate */
            new_size = lines_allocated*2;
            array = (char **)realloc(array,sizeof(char*)*new_size);

            if (array==NULL) {
                fprintf(stderr,"Out of memory.\n");
                exit(3);
            }

            lines_allocated = new_size;
        }

        /* Allocate space for the next line */
        array[il] = malloc(max_line_len);
        if (array[il]==NULL) {
                fprintf(stderr,"Out of memory (3).\n");
                exit(4);
            }
        if (fgets(array[il], max_line_len-1, file)==NULL)
            break;

        /* Get rid of CR or LF at end of line */
        for (j=strlen(array[il])-1;j>=0 && (array[il][j]=='\n' || array[il][j]=='\r');j--)
            ;

        array[il][j+1]='\0';
    }

    /* Close file */
    fclose(file);

    /* Print and free the every element of the array */
    int cc;
    for (cc = 0; cc < il; cc++) {
        printf("%s\n", array[cc]);

        /* Free the every element of the array */
        free(array[cc]);
    }

    /* Free hole array */
    free(array);

    return 0;
}

valgrind ./main

valgrind --leak-check=full --show-reachable=yes ./main
==4806== Memcheck, a memory error detector
==4806== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4806== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==4806== Command: ./main
==4806== 
1
2
3
4
5
6
7
8
9
10
11
==4806== 
==4806== HEAP SUMMARY:
==4806==     in use at exit: 50 bytes in 1 blocks
==4806==   total heap usage: 14 allocs, 13 frees, 2,192 bytes allocated
==4806== 
==4806== 50 bytes in 1 blocks are definitely lost in loss record 1 of 1
==4806==    at 0x4C2AC3D: malloc (vg_replace_malloc.c:299)
==4806==    by 0x40092E: main (in /var/www/mem/main)
==4806== 
==4806== LEAK SUMMARY:
==4806==    definitely lost: 50 bytes in 1 blocks
==4806==    indirectly lost: 0 bytes in 0 blocks
==4806==      possibly lost: 0 bytes in 0 blocks
==4806==    still reachable: 0 bytes in 0 blocks
==4806==         suppressed: 0 bytes in 0 blocks
==4806== 
==4806== For counts of detected and suppressed errors, rerun with: -v
==4806== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

如何正确释放内存?它说应该再释放一块内存,但它在哪里呢?

4 个答案:

答案 0 :(得分:10)

for (cc = 0; cc < il; cc++) {

如果ilarray的有效索引(并且它是),则循环中的比较应为:

for (cc = 0; cc <= il; cc++) {

以触发array的最后一个元素(并释放其内存)。

答案 1 :(得分:5)

只需替换

for (cc = 0; cc < il; cc++)

for (cc = 0; cc <= il; cc++)

要弄清楚这一点,想象一下如果分配循环for (il = 0; 1; il++)只迭代一次会发生什么。在这种情况下,控件未达到il++,因此il保持为零,for (cc = 0; cc < il; cc++)迭代零次。在一般情况下,释放循环使得一次迭代小于分配循环。

答案 2 :(得分:3)

您的代码泄漏了上次分配,因为ilfgets(array[il], max_line_len-1, file)返回NULL时永远不会增加。{/ p>

array[il] = malloc(max_line_len);及其NULL检查移至fgets之后将解决此问题。这种方法的另一个好处是,您可以分配确切的大小,而不是在max_line_len分配。

// Check that we will need the allocation
char temp[max_line_len];
if (fgets(temp, max_line_len-1, file)==NULL) {
    break;
}
// Allocate only when we are sure that we are going to need it
temp[max_line_len-1] = '\0';
size_t len = strlen(temp);
array[il] = malloc(len+1);
if (array[il]==NULL) {
    fprintf(stderr,"Out of memory (3).\n");
    exit(4);
}

注意:realloc分配回正在重新分配的变量可能会导致先前已分配给该变量的内存泄漏。这不是您的代码中的问题,因为您立即致电exit(4),但您应该了解此作业的一般问题。

答案 3 :(得分:2)

如果您遇到各种各样的问题,并且混合调用各种分配器,并且对事物非常苛刻,那么为各种内存分配器实现包装器(这可以使用宏巧妙地完成)缓存新分配的缓冲区的地址(例如,堆栈顶部)然后 - 在某个时刻 - 导航堆栈并释放所有人。 不要将随机调用混合到free()或其类似物中。当某些东西被释放时,用零覆盖这些东西,这样你就不会不小心再次尝试free(),这会让free()感到不安。

如何巧妙地使用MACROS(我说过,所以我现在最好让它工作)并避免递归问题:

让我们使用malloc()作为我们的第一个受害者。

在另一个源文件中,创建一个调用_malloc()的函数malloc()

在包含所有内存分配和释放的源文件中,按如下所示定义malloc()

#define malloc( n )  ( *sp++ = _malloc( n ) )

必须将代码作为前导码调用,以设置堆栈并在其基础上指向sp。让它变得美好而大:你会感到惊讶多少次malloc()及其兄弟可能最终被召唤。在不同的时间 - 实际上,恰当的时候 - 调用你自己的free_all()执行此操作:

void free_all() {  
  while( --sp >= base_of_malloc_buf_stack ) {  
    free( *sp );   
    *sp = 0; /* avoid future re-free() */    
  }  
}