• Memory leakage

    From Björn Felten@2:203/2 to All on Sun Jan 23 12:56:31 2022
    Someone mentioned memory leakage here some time ago. I notice that too. It's only one percent or so, of the available 2GB, per week, so not all that important.

    But it builds up over time until I finally need to perform a reboot -- for that reason only. I usually can maintain an uptime of years if
    not for the binkd leak.



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Oli@2:280/464.47 to Bjrn Felten on Sun Jan 23 13:10:37 2022
    Björn wrote (2022-01-23):

    Someone mentioned memory leakage here some time ago. I notice that too. It's only one percent or so, of the available 2GB, per week, so not all that important.

    But it builds up over time until I finally need to perform a reboot
    -- for that reason only. I usually can maintain an uptime of years if not for the binkd leak.

    Why reboot? Isn't the lost memory freed after binkd has been terminated?

    ---
    * Origin: Birds aren't real (2:280/464.47)
  • From Alexey Fayans@2:5030/1997 to Bjoern Felten on Sun Jan 23 15:58:45 2022
    Hello Bjoern!

    On Sun, 23 Jan 2022 at 12:56 +0100, you wrote to All:

    But it builds up over time until I finally need to perform a reboot
    -- for that reason only. I usually can maintain an uptime of years if
    not for the binkd leak.

    If you need to reboot PC to free up memory, then the problem is definitely not with binkd.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Bjrn Felten@2:203/2 to Oli on Sun Jan 23 19:55:16 2022
    Why reboot? Isn't the lost memory freed after binkd has been terminated?

    Well, if that was the case, I wouldn't regard it as leakage. No, it isn't. Can it be some cache grabbing that isn't done correctly?

    I've always thought it was related to the badly written WinAPI calls for cache usage, but then I saw someone else mentioning it, so I thought I'd bring it up. As I said -- no big deal.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Björn Felten@2:203/2 to Alexey Fayans on Sun Jan 23 19:57:19 2022
    If you need to reboot PC to free up memory, then the problem is
    definitely not with binkd.

    Thanks for your helpful input. Keep up the good work!



    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Oli@2:280/464.47 to Bjrn Felten on Mon Jan 24 20:17:17 2022
    Bj_rn wrote (2022-01-23):

    Why reboot? Isn't the lost memory freed after binkd has been
    terminated?

    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.

    No, it isn't. Can it be some cache grabbing that isn't done correctly?

    I've always thought it was related to the badly written WinAPI calls for cache usage, but then I saw someone else mentioning it, so I thought 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)