: > is not static, so the mem estimator would count that as ram used by the : > object itself. : : The estimation actually includes static fields -- if it didn't you : could easily overflow memory simply by allocating static byte[]
But clearly there is a diff between statics in the tests, and statics in classes of objects held onto by the test -- otherwise we should have started seeing way more "clean up your statics" failures then this when the Logger changes got committed. this test seemed to be the touchstone because... * the test maintained a static, un-nulled out, SolrRequestParser * SolrRequestParser instance have non-static refrences to a Logger ...surely if the SolrRequestParser *class* had a static var the Logger (instead of an instance var) that wouldn't have counted against the amount of memory being used by the SolrRequestParser ? i mean ... if the static vars in every class were counted against the objects of that class, the RAM estimater would be virtually useless. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
