yrdl

Since it seems to be a problem that only occurs on a few specific systems, it would be hard to track down and maybe they just don't want to commit resources to fix something that only happens to a few people. I say few because I only see a couple mentioning it and also because I am running free BD on 3 computers with 3…

I don't know what resource monitor that screenshot is showing but I still think it's saying that gzserv is only using 75mb of your memory. The working set includes private as well as shared memory and only shows 75mb. Private bytes in that program may not mean physical memory. Alternatively, it may be reserving physical…

Also, the commit size is irrelevant since that is virtual memory not physical. Right now mine says this: Working set (total physical memory in use)-14.3mb, Private--8.3 mb, Shared--6.0mb It peaked at : Working--43.6mb, Private---37.9mb, Shared---3.7mb Note that my screenshot is showing that it uses 8GB for the private…

I was wondering why I was low on memory. Turns out gzserv was hogging 8GB of RAM.