Is this a general problem with Windows crash uploads, or something specific to my dump-on-DCHECK?  The latter was specifically not set up to log the DCHECK text, in an effort to avoid bloating the build with those strings (as discussed offline, we'll look at leaving them in for the retry!)

The dump without crashing code doesn't even keep the string on the stack so yes this is an issue with the dcheck-dump code.

Overall we would also like for these messages to land in a crash key of its own but that's another story.

Re #2: Yes, I know the dump-on-DCHECK behaviour; I did that deliberately (though based on your feedback I'll be revising the patch in that respect).

My question was which issue this bug refers to - do you have a separate bug for the crash-key integration, or do we need to file one?

Ok this bug is about the first point (filled before we had similar discussion over email, feel free to handle the way you prefer).

For the crash key integration there wasn't one but I just filled  issue 602285  for it, thanks.

Marking WontFix, since this behaviour matches that of CHECK, and we don't want dump-on-DCHECK to cause additional bloat of the binary.