MSGID: 2:5020/2141.808 ce9b96b5   
   REPLY: 2:240/12 600378ad   
   PID: Hotdoged/2.13.5/Android   
   TID: jNode/Android   
   CHRS: CP866 2   
   Hello, Gerrit Kuehn.   
   On 4/16/21 8:44 AM you wrote:   
      
    MK>> After +20 some odd years I have yet to see that happen.   
    GK> Just start an application that runs into a memory leak...   
      
   --------cut memleak.c -------   
   #define gigs = 8 // your gigabytes here   
   #include    
   int main() {   
     long int i=0;   
     while(i<1024*1024*1024*gigs/2) {   
       void *nofree = malloc(++i);   
     }   
     return 0;   
   }   
   ---------cut-------   
      
   Try this w/ gcc -o memleak memleak.c; ./memleak   
      
   No free() after malloc() should give memory leak, isn't it?   
      
   --   
   Best regards!   
   Posted using Hotdoged on Android   
   --- Hotdoged/2.13.5/Android   
    * Origin: Android device, Milky Way (2:5020/2141.808)   
   SEEN-BY: 1/123 50/13 109 90/1 103/705 105/81 114/709 120/340 123/131   
   SEEN-BY: 124/5016 129/305 154/10 203/0 221/0 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 452 550 616 664 700 1016 1017 240/5832 249/110   
   SEEN-BY: 249/206 317 400 280/464 5003 282/1038 288/100 292/854 8125   
   SEEN-BY: 301/1 310/31 317/3 322/757 342/200 396/45 423/120 463/68   
   SEEN-BY: 467/888 633/280 712/848 770/1 2452/250 5000/111 5001/100   
   SEEN-BY: 5005/49 5012/200 5019/40 42 5020/400 545 828 830 846 848   
   SEEN-BY: 5020/1042 1477 2047 2140 2141 4441 12000 5025/3 5028/66 5030/1081   
   SEEN-BY: 5030/1900 1957 2404 5036/26 5037/7 5053/58 400 5054/8 5060/900   
   SEEN-BY: 5063/89 5064/56 5066/18 5080/102 5083/444 5095/20   
   PATH: 5020/2141 2140 1042 4441 545 280/464 229/101 426