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.
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?
If you need to reboot PC to free up memory, then the problem is
definitely not with binkd.
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.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 93 |
Nodes: | 16 (0 / 16) |
Uptime: | 05:13:04 |
Calls: | 5,157 |
Calls today: | 2 |
Files: | 8,491 |
Messages: | 352,740 |