Re: free seems not work
- Posted by PtitChaud Feb 23, 2011
- 1558 views
Thank's for your answer,
today with the same code, i've done this 2 tests:
-1- a loop with 10 iterations of 10MB, allocated and freed
At the start, the private memory was 8MB and at the end the same. With WMMAP.EXE, i saw that after the free_bcl() procedure, all the allocated memory was released.
-2- a loop with 100*1024 iterations of 1024bytes, allocated and freed.
The amount of the allocated memory is the same than in the first test.
At the start, the private memory was nearly the same than in the first test : 8MB, but at the end, the private memory was 29MB
Ok, 21MB is perhaps necessary to internal Euphoria functions to improve the performance, reuse memory ...and not a bug
So, when i use ODBC, the result of the querie is stored into a sequence with elements. The first element contains the name of the each column and the next elements contain the values. After, with a loop, each element (each row) stored in the result sequence is stored into another very big sequence with an other loop to store one by one each value. Many usage of temporaly sequences and atoms and with différent length. So in this case, would it be better to use allocated user memory instead of temporaly sequences and avoid the memory needed by internal euphoria functions ? what are the good practices ?
Thank's for Euphoria and any help to how to do to find why private memory grow up.
