Chromium code uses PostTask a lot to do a poorman's version of continuation passing style.

Thus, a "backtrace" is often incomplete because it terminates at the most recently executed task. The FROM_HERE/posted_from token helps give 1 frame of context, but what's often wanted is a short record of all the various asynchronous posts.

This can fairly easily be implemented by adding a short array of program_counters providing a breadcrumb (or async backtrace) of posted_from records. This array can then be copied onto the stack during a task execution and aliased to ensure the compiler does not optimize it out.

Because it is on the stack, it will be captured in crash dumps.

There will need to be tooling in the crash processing system to recognize and symbolize this object, but at least the data will be there.

The performance impact of this will be the equivalent of a 4 word copy per post-task. Almost certainly eaten by the pipeline.