Ok thanks. The reason I would like to audit memory usage is that OSes can
have different strategy for allocating memory, including having some memory
reported as used but not actually wired. We never had any memory issues
with that part of the code before and it hasn't changed much so I'm tempted
to push the investigation further to see if this is actually a real problem
or just a reporting issue.
2017-12-21 19:04 GMT-06:00 p g <pra...@gmail.com>:
> some more insight on windows 'memory leak'.
>
> at first i thought it would grow steadily and indefinetly but well... i
> let it grow these days and what i'm seeing now is process consuming 2G of
> RAM. it's quite an amount compared with more or less steady 40M usage of my
> 'simpler' radio.
> well, at least it doesn't eat up all available ram...for now :)
>
> what is good for that early stage is that it doesn't seem to be unstable.
> haven't crashed although various sources have been connecting and
> disconnecting, files were written to disk, playlists changing...
>
>
>
> p
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Savonet-users mailing list
> Savonet-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
