Rich Freeman wrote: > On Mon, Nov 26, 2018 at 6:16 PM Alan Grimes <alonz...@verizon.net> wrote: >> Programmers these days don't seem to have any concept that memory is >> finite and that it's usage should be optimized. =| >> > I have it on good authority that unused memory is wasted memory. It > is a good thing that I never run more than one process a time so that > my browser is correct in assuming that the OS wouldn't possibly be > able to find a better use for the RAM than that tab I haven't clicked > on in 20 minutes that is running some javascript with more lines of > code than the sorts of operating systems people actually used back > when they didn't run more than one process at a time... >
This is true. I tend to have a lot of tabs open at times when I'm trying to find something. Or, trying to see if I can find something better. Thing is, as with most of us I guess, we only SEE one tab at a time. While Firefox did seem a little faster to respond, it sure did hog up some memory. I'd rather have it less memory hungry right now. To add to the original post. I have been using another file manager, PCMan, since yesterday. It doesn't have that nifty little video viewer on the right side but so far, memory usage has been normal. The command X in top shows the previous normal usage of a few hundred MBs of memory. It was a few to several GBs and increasing when having the out of memory problem. With what may be a process of elimination, it seems Dolphin may be the issue. I'm sure Firefox hogging up more than its share didn't help any tho. ;-) If anyone sees something that points to something else, please post. May just have to wait on a new update to Dolphin. I think they do that about once a month or so. Dale :-) :-)
