On Monday, May 2, 2016 at 4:35:33 PM UTC-7, Nicholas Nethercote wrote: > > - Should we look at how to make browser not a pain in debug builds (will > > make it harder to get the expected asserts)? Hoping that more people run it? > > Or will people still not run debug builds. > > - Should we look into running those asserts in release builds (on nightly) > > on a not often 'random' bases? Making sure it doesn't hurt performance too > > much? > > I suspect the random idea is more practical.
This is, AIUI, what Chome does. Running asserts at some low frequency is not a new idea. We've kicked it around on JIT for the last few months. Another simliar idea is to take more diagnostic information (such as the jitcode Nicolas suggested) One advantage is that if something spikes in crashes, the liklihood that your random debug information collection hits one of them goes up. It seems like a perfect low-but-constant-overhead solution to release data collection. Eric _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
