> On Oct 17, 2019 w42d290, at 10:09 PM, Parke <parke.ne...@gmail.com> wrote: > > On Thu, Oct 17, 2019 at 12:53 PM Adrien Monteleone > <adrien.montele...@lusfiber.net> wrote: >> try: `man free` > > I already read parts of `man free`. It did not explain to me what on > my system was using the RAM reported as being `used`. >
That’s not what I meant. I mentioned that because the man page explains what the output numbers represent. The tool won’t tell you specifics of what is the cause of any of them. >> But try `free` without `-h` so you see the output in bytes and do the above >> equation by hand. You should see every byte is accounted for. > > The numbers add up. I just cannot tell what is using the `used` > memory. It is not being used (as far as I can tell) by any of the > programs listed by `top`. No, they don’t add up, and there isn’t some mystery ‘used' out there. See the man page again for explanations of the columns and the equation I gave (which is from the explanations) Used = total - free - buff/cache Your equation is incorrect. You are doing: Used - buff/cache = ??mystery?? ‘Used’ is derived by subtracting free and buff/cache from total Subtracting buff/cache again from ‘used’ is meaningless. And what I mean by “not adding up” is that your output shows: Total = 15G, Used = 4.2G, Free = 9.5G, and Buff/Cache = 1.9G But that would render the following when plugged in: 4.2G = 15G - 9.5G - 1.9G Which is not true. 15G - 9.5G - 1.9G = 3.6G, not 4.2G Not using the ‘human readable’ ‘-h’ flag will show you actual bytes. If you do so, that math should work out, to the byte. (as long as you use the correct equation) But all of that isn’t really important for the crash/hang problem. > >> Do you get any errors or warnings when running GnuCash from the command line? > > No errors. > >> Did you manage to examine the tracefile after a crash/hang? > > My apologies, but I do not know how to reliably reproduce the freeze. > (It can take 10 to 60 minutes of working with GnuCash until a freeze > occurs.) I do not have the time at present to investigate further. I > reported this issue primarily to create a record in case other people > encounter the same issue in the future. > > I expect to either switch to Ubuntu 19.10, or to install a newer > version of GnuCash via flatpack. If thereafter I again encounter the > freeze, I will provide additional updates. > > Thanks again for all your assistance. I do appreciate it. Fair enough. It might be lots of work and chasing something hard to pin down anyway. The easier path certainly is to just upgrade. Regards, Adrien _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
