As I'd hoped my post would have made clear, my immediate situation is a very temporary one. One that you could have treated as a stroke of luck, for it caricatures the very real situation that others are seeing, but because the amount of memory on their systems is in excess of the amount you have specified as a minimum, they have have had more difficulty than I've had with the main task that is an end-user's responsibility in such a situation: that of delivering to maintainers a means for reproducing the problem that they are seeing.
In the relevant (to this discussion) portions of the 40+ years I have spent in the field of computer science, I have diagnosed and resolved countless difficult bugs and escalations at both user-level and deep within the guts of the UNIX kernel. In doing so, I have experienced many times just how difficult it can sometimes be to obtain data that is of sufficient quality and/or quantity to help reproduce a reported problem.
To be handed an a new insight into an existing problem that has been reported by others is a gift
To turn that gift on its head, and suggest that the person giving you that gift was wrong to do so is a kind of hubris that is ultimately going to do harm to your product.
If I were one of the earlier individuals who had described having this issue (on systems that exceed the memory requirements
stated in your reply to me) I would be outraged at such dismissal of additional data that a third party had taken the time and trouble to provide you with to help in the investigation of the problem I'd previously reported.
When I first read about Pale Moon, not very long ago, I had high hopes for it.
I'm researching the purchase of a new computer, "as we speak".
I'm also learning about Pale Moon's support, both from posts on other sites and in these forums. And I've discovered that your response to the assistance I tried to provide is not unusual. It conforms to a trend in how "uncomfortable issues" appear to be dealt with here. (In fact, after reading about the trumpish manner in which NoScript had been labeled malware
, I half-seriously actually had expected
the information I was providing to be treated with dismissal.)
Some of the following, which range from probable to quite certain, may be under your control, and some may not be:
- I'm going to replace my damaged and hopelessly inoperative computer soon, after which
- this low-memory computer shall go back to the closet, and
- you may continue to dismiss a very real macro-level memory leakage issue, and
- if there are further posts about it, you may find ways to dismiss those too.
- Since Pale Moon is too good to have real problems, there will be other issues reported that are also dismissed
- The number of un-problems may continue to accumulate, and maintainer frustration with end-users may mount.
- The number of un-problems has the potential to become so great that most copies of Pale Moon could end up being "relegated to the closet".