use Perl

• Check for this (and other things) with Devel:Size (Score:1)

  by Elian (119)

  You can see this in action by looking at the size of the scalar with the Devel::Size module. You can see similar things with arrays when you shrink them down.
• Reallocation (Score:2)

  by petdance (2468)

  And, of course, even if all memory for that string is deallocated, Perl hangs on to it and never gives it back to the OS. This is a common question on mod_perl lists: "My Apache children just keep on eating memory!"

  --
  

  --
  xoa
  • Re:Reallocation (Score:1)

    by jplindstrom (594)

    Yeah, but that's something else, that deallocated memory doesn't go back to the OS.
    
    In this case it doesn't even go back to Perl, and that's a little worrisome if you occasionally get a peak of huge indata.
    
    To me that doesn't matter _that_ much since I tend to avoid long running processes, restarting the program every once in awhile. Even if Perl behaves and you code your stuff the right way, there is always some module that will mess up and not break a circular reference, or some external lib will forget t
  • Re:Reallocation (Score:2)

    by jhi (318)

    What is this rampant fallacy of applications giving memory back to the OS? That is completely dependent on the implementation of the malloc, and in many systems the (virtual) memory use never goes down, only up. I think glibc malloc does memory allocation using mmap(), and the munmap() by free() does make the process virtual memory use go down. But nevertheless, expecting free() (or at Perl level, undef()) to make one's memory use (as shown by, say, ps), is a false assumption. Completely explaining it re