Cameron McCormack <c...@mcc.id.au> writes: > (I wonder if we could collect all the same data, and use the same > crash reporting infrastructure, for non-crashing crash reports like > this.)
For what it's worth, I've done something very close to this *accidentally*, on Linux, by manually sending a crash signal to test crash reporting and hitting bugs in how the signal is re-raised, such that it just returns to the not-really-crashed code. (It does unhook the signal handlers, so the next crash will kill the process, but that could be changed.) I never tried to make it an actual feature -- I had concerns about rate limiting, and maybe some other things I've forgotten, and then the work that's been mentioned here about telemetry seemed like it was solving the same problem in a more generally useful way. It would have been useful for desktop Linux sandboxing, because there are cases where we don't need to crash, and want to avoid crashing if possible on release, but we'll likely need at least a crash report's worth of info to figure out what's going on; instead we settled for crashing only on Nightly. --Jed [1] https://searchfox.org/mozilla-central/rev/0b8ed772d24605d7cb44c1af6d59e4ca023bd5f5/toolkit/crashreporter/breakpad-client/linux/handler/exception_handler.cc#398 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
