Specify a file size limit for minidumps

Specify a file size limit for minidumps

When there are upwards of 200 threads in a crashing process, each having an
8KB stack, this can result in a huge, 1.8MB minidump file.  The Crash Server
throws away any uploaded file larger than 1.2MB.  Setting the minidump size
limit (see https://breakpad.appspot.com/487002/) will result in less stack
being dumped when there are so many threads.

BUG=chromium-os:31447, chromium:154546
Contributed by Michael Krebs <mkrebs@chromium.org>;

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=169221

[Michael Krebs, 2012-10-13 05:58:33]

Note, this CL can't be committed until https://breakpad.appspot.com/487002/ is
committed and included in Chrome's Breakpad.

Lei, would you be able to commit this change for me after the Breakpad change
goes in?  ...I'm not a Chromium committer.

Also, is there a good way for me test that this change doesn't break anything? 
I can try to get Chrome building, but I wasn't sure if there was an easier way
for people who don't regularly work on Chrome.

[Michael Krebs, 2012-11-16 01:37:49]

Lei, with the corresponding Breakpad changes in now, would you be able to take a
look at this CL?  For testing, would the trybots be sufficient?  ..not being a
committer, though, I don't think I can even run the trybots on this change.

[Lei Zhang, 2012-11-16 21:18:15]

lgtm

If it builds for you locally with breakpad turned on, that's good enough. Let me
know if you are ready to commit and I'll put it in the commit queue.

[Michael Krebs, 2012-11-22 02:34:54]

It builds now in my local checkout.  So it should be ready to commit.

[commit-bot: I haz the power, 2012-11-22 02:55:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mkrebs@chromium.org/11142010/14001

[commit-bot: I haz the power, 2012-11-22 04:54:45]

Change committed as 169221