REPLY: 2:203/2 61eda48e   
   MSGID: 2:280/464.47 61eefb3d   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: UTF-8 4   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Bj_rn wrote (2022-01-23):   
      
    O>> Why reboot? Isn't the lost memory freed after binkd has been   
    O>> terminated?   
      
    BF>     Well, if that was the case, I wouldn't regard it as leakage.   
      
   On a modern mainstream OS, the mess is cleaned up after the application has   
   been terminated, but it's still called memory leak.   
      
    BF> No, it isn't. Can it be some cache grabbing that isn't done correctly?   
      
    BF>     I've always thought it was related to the badly written WinAPI calls   
    BF> for cache usage, but then I saw someone else mentioning it, so I thought   
    BF> I'd bring it up. As I said -- no big deal.   
      
   What do I know about Windows ... ;).   
      
   The support hotline would suggest to upgrade to the newest version and try   
   again.   
      
   2:203/2's binkd is 7 years old.   
      
    * Origin: Birds aren't real (2:280/464.47)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10   
   SEEN-BY: 203/0 218/840 220/70 221/0 226/17 30 227/114 229/110 200   
   SEEN-BY: 229/206 307 317 424 426 550 664 700 240/5832 250/5 8 266/512   
   SEEN-BY: 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25 301/1   
   SEEN-BY: 305/3 310/31 317/3 320/219 322/757 341/234 342/200 396/45   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 100 340 772/210 220   
   SEEN-BY: 772/230 2452/250   
   PATH: 280/464 770/1 317/3 229/426