#522 test_memory is failing on Fedora Rawhide

v1.0 (example)
4 days ago

Running test_memory on Fedora Rawhide fails:

% TEST_MEMORY: reported memory consumption should increase after allocating a big array!
% TEST_MEMORY: start = 3994832, end = 3994736

On F18 I get:

% TEST_MEMORY: start = 4777296, end = 5577056

No idea what is going on here.

diff -up gdl-0.9.3/testsuite/test_memory.pro.tests gdl-0.9.3/testsuite/test_memory.pro
--- gdl-0.9.3/testsuite/test_memory.pro.tests 2012-12-27 09:22:44.000000000 -0700
+++ gdl-0.9.3/testsuite/test_memory.pro 2013-03-21 10:38:49.419098783 -0600
@@ -1,6 +1,7 @@
pro test_memory
mem = memory(/curr)
a = dblarr(99999)
+ message, 'start = '+string(mem)+', end = '+string(memory(/curr)), /conti
if mem ge memory(/curr) then begin
message, 'reported memory consumption should increase after allocating a big array!', /conti
exit, status=1


  • Alain C.

    Alain C. - 2013-04-22

    in OSX, SunOS and with 32bits Linux, we know how to monitor the RAM usage and freeing.
    (usage ? testing in CLI that we have memory leak ! Would be nice is some cases in the past !!)
    We don't found a reliable way on 64bits Linux. 3 years ago we spend some time with a student and Sylvester, just finding it is not trivial on 64b linux.

    Help welcome !


  • Sylwester Arabas


    Apparently, the GNU time utility is able to measure the memory usage by making use of the information available via wait() calls - perhaps it could be used to implement it. Here's the source:

    I'll try to look at it but not during the next few days - posting this info just in case someone might have time to look at it earlier.


  • Sylwester Arabas

    • status: open --> closed
    • Group: --> v1.0 (example)

Log in to post a comment.