It may be possible to narrow down the performance-regressing MOZ_ASSERTs by pushing a series of Talos try runs with MOZ_ASSERT enabled for specific top-level directories - then take those with significant regressions, and recurse down a layer, lather, rinse, repeat to at least the leaf-dir level, or (if there are a lot in the dir) the file level.
Then we can look with eyeballs and figure out what's up. It might also be possible to use trace APIs to measure the cost of each assertion... though the traces themselves might swamp most assertion costs. -- Randell Jesup, Mozilla Corp remove "news" for personal email _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
