[sql] Lower SQLITE_PRINTF_PRECISION_LIMIT for fuzzer.

[sql] Lower SQLITE_PRINTF_PRECISION_LIMIT for fuzzer.

Real-world usage should never involve precisions above maybe 100.  The
previous limit of 128M makes it very easy to blow out memory when
fuzzing, and since OOM is already fatal, I'm not sure that such a
large limit provides any productive coverage beyond something more
reasonable.

BUG=665292
R=mmoroz@chromium.org

Review-Url: https://codereview.chromium.org/2641123004
Cr-Commit-Position: refs/heads/master@{#445080}
Committed: https://chromium.googlesource.com/chromium/src/+/9b1279144e1a29b56992dd6e5bf233f5889cc583

[Scott Hess - ex-Googler, 2017-01-19 21:58:38]

The CQ bit was checked by shess@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-19 21:59:26]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Scott Hess - ex-Googler, 2017-01-19 21:59:57]

SQLITE_PRINTF_PRECISION_LIMIT from 128,000,000 to 1,280,000.

[Now I'm thinking "Why not 1,000,000", but whatever.]

[commit-bot: I haz the power, 2017-01-19 23:14:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-19 23:14:02]

Dry run: This issue passed the CQ dry run.

[mmoroz, 2017-01-20 09:36:13]

LGTM

1,280,000 is kind of mysterious comparing to 1M, I like it! :)

Thanks Scott!

[Scott Hess - ex-Googler, 2017-01-20 17:05:46]

The CQ bit was checked by shess@chromium.org

[commit-bot: I haz the power, 2017-01-20 17:06:07]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-20 17:10:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484931946921810, "parent_rev":
"f623c0b50e5dec7eafdfc5699412ea60548471a2", "commit_rev":
"9b1279144e1a29b56992dd6e5bf233f5889cc583"}

[commit-bot: I haz the power, 2017-01-20 17:10:31]

Description was changed from

==========
[sql] Lower SQLITE_PRINTF_PRECISION_LIMIT for fuzzer.

Real-world usage should never involve precisions above maybe 100.  The
previous limit of 128M makes it very easy to blow out memory when
fuzzing, and since OOM is already fatal, I'm not sure that such a
large limit provides any productive coverage beyond something more
reasonable.

BUG=665292
R=mmoroz@chromium.org
==========

to

==========
[sql] Lower SQLITE_PRINTF_PRECISION_LIMIT for fuzzer.

Real-world usage should never involve precisions above maybe 100.  The
previous limit of 128M makes it very easy to blow out memory when
fuzzing, and since OOM is already fatal, I'm not sure that such a
large limit provides any productive coverage beyond something more
reasonable.

BUG=665292
R=mmoroz@chromium.org

Review-Url: https://codereview.chromium.org/2641123004
Cr-Commit-Position: refs/heads/master@{#445080}
Committed:
https://chromium.googlesource.com/chromium/src/+/9b1279144e1a29b56992dd6e5bf2...
==========

[commit-bot: I haz the power, 2017-01-20 17:10:32]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/9b1279144e1a29b56992dd6e5bf2...