On Mon, Jul 27, 2015 at 2:35 AM, Karl Tomlinson <mozn...@karlt.net> wrote: > Sometimes it would be nice to check in crashtests that use, or > attempt to use large memory allocations, but I'm concerned that > checking in these crashtests could disrupt subsequent tests > because there is then not enough memory to test what they want to > test.
It seems like it should be a goal that we continue to operate successfully after navigating away from a page that uses a large amount of memory. In practice ... > Is anything done between crashtests to clean up memory use? > Or can CC be triggered to run during or after a particular crashtest? Nothing other than the normal heuristics. If you look at logs from a debug build you'll see points where we do a GC/CC and clean up windows from the last several tests. > Do crashtests go into B/F cache on completion, or can we know that > nsGlobalWindow::CleanUp() or FreeInnerObjects() will run on completion? That I don't know, but it should be easy to test locally. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
