Databases
StackOverflow2013
Postsdbo
POUnable to find simple memory leak
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to find simple memory leak
    primarykey
    data
    text
    <p>Can someone please help me find the memory leak which is occurring here? I am just attempting to load a 1600x960 24bit RAW image (46,08,000 bytes) into memory using an Image class I designed. In memory its taking 30MB, as I see in task manager..</p> <p>Even after the destructor is called (going out of scope) it still takes up 2M. Please help!</p> <pre><code>#include &lt;cstdio&gt; #include &lt;iostream&gt; struct pixel { char* color; // to support various BPP }; class Image { private: pixel** image; int width; int height; int BPP; // bytes per pixel int size; // in bytes public: Image(std::string src, int width, int height, int BPP); ~Image(); pixel** get_matrix(int col, int row, int BPP); }; pixel** Image :: get_matrix(int col, int row, int BPP) { pixel** matrix = new pixel*[row]; for(int i=0 ; i&lt;row ; i++) { matrix[i] = new pixel[col]; for(int j=0 ; j&lt;col ; j++) matrix[i][j].color = new char[BPP]; } return matrix; } Image :: Image(std::string src, int width, int height, int BPP) { FILE *in; if( (in = fopen(src.c_str(), "rb")) == NULL ) image = NULL; else { this-&gt;height = height; this-&gt;width = width; this-&gt;BPP = BPP; this-&gt;size = width*BPP*height; image = get_matrix(width,height,BPP); char* buffer = new char[size]; fread(buffer, sizeof(char), size, in); int l=0; for(int i=0 ; i&lt;height ; i++) { for(int j=0 ; j&lt;width ; j++) { for(int k=0 ; k&lt;BPP ; k++) image[i][j].color[k] = buffer[l++]; } } delete []buffer; fclose(in); } } Image :: ~Image() { for(int i=0 ; i&lt;height ; i++) { for(int j=0 ; j&lt;width ; j++) delete []image[i][j].color; delete []image[i]; } delete []image; } int main() { { getchar(); Image in("x.raw", 1600, 960, 3); getchar(); } getchar(); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBruce
    1. USBruce
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnable to find simple memory leak
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POUnable to find simple memory leak
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POUnable to find simple memory leak
      1. This table or related slice is empty.
      1. VTDownMod
    1. CO1) Are you sure this is a memory leak? What tool are you using? 2) You could omit the file I/O, initialize the colors to {0,0,0} and simplify things.
      singulars
      1. POUnable to find simple memory leak
      1. USBeta
    2. CO@Beta I am using Codeblocks on Win7, using Process Explorer to see memory usage. I'll try what you said
      singulars
      1. POUnable to find simple memory leak
      1. USBruce
    3. COI don't see any leak, either. If you are working on the class anyway, you should pass the string argument to the constructor as a reference, i.e. `const std::string& src`. Right now you are making an unnecessary copy. I mention this because passing copies instead of references can quickly become a bad habit.
      singulars
      1. POUnable to find simple memory leak
      1. USherzbube
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload