> Well, then the stategy is not to have a strategy, which is perfectly fine.
The strategy is to teach the principle of not over commiting. > It still doesn't matter for the use case under discussion here. The "bug" > reporter expected some OOM type situation, and didn't observe any, because > the reported "memory leak" does not exist. Case closed, original bug report > in the "rejected" queue, bug reporter educated about file system cache. Sometimes I wonder if we should remove all the diagnostic tooling.
