Technically, these are not leaks, but the effect is similar :) When running certain non-stop browser tests, such as DOM-Hanoi (see bug URL), Safari memory usage grows fast, because Obj-C autoreleased objects do not get a chance to be collected. I suspect they may fill the address space before the test actually finishes, but I was not patient enough to stand the paging. All such allocations are made inside FrameMac::setStatusBarText(), so I gave this method an autorelease pool of its own.
Created attachment 9409 [details] proposed patch
Comment on attachment 9409 [details] proposed patch Looks good. r=me But are there any other calls besides "set status bar text" that need an autorelease pool for the same reason?
(In reply to comment #2) > But are there any other calls besides "set status bar text" that need an > autorelease pool for the same reason? This patch fixes all DOM-Hanoi "leaks". Perhaps, other tests will uncover more?
Darin, should this patch be committed now, or should it wait until after the stabilization period?
(In reply to comment #4) > Darin, should this patch be committed now, or should it wait until after the > stabilization period? I think it's good to land this now.
Committed revision 15405.