O(n) vs O(bigger than I wanted) RT @bz_moz: Memo for bug filers: "memory leak" and "memory usage" are not the same thing.
-
-
Replying to @littlecalculist
@littlecalculist@bz_moz Given how hard it is for _us_ to get enough insight to differentiate such cases, maybe forgive the bug filers :)2 replies 0 retweets 0 likes -
Replying to @graydon_pub
@graydon_moz@bz_moz True... in fact I honestly have no idea how to diagnose memory consumption problems.1 reply 0 retweets 0 likes -
Replying to @littlecalculist
@littlecalculist@graydon_moz It starts depending on application. But as a first cut, stable memory usage == "not leak". With caveats. ;)1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@littlecalculist@graydon_moz In Fx, I'd say caching/fragmentation is ok; doing X a second time should peak no higher than first.4 replies 0 retweets 0 likes -
Replying to @davidbaron
@davidbaron@bz_moz@littlecalculist There's fast growth and slow growth. It's a complex program. Still 2x resident after 24h, for me.2 replies 0 retweets 0 likes
@graydon_moz @davidbaron @littlecalculist Sure. I'm not saying there are no leaks! The testcase that prompted my tweet is likely not one.
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.