Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org

Committed: https://crrev.com/9cd13f726995393db68768a714049ea7650b9f86
Cr-Commit-Position: refs/heads/master@{#403824}

[Justin Novosad, 2016-07-05 20:12:04]

Description was changed from

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
==========

to

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org
==========

[Justin Novosad, 2016-07-05 20:12:12]

The CQ bit was checked by junov@chromium.org

[commit-bot: I haz the power, 2016-07-05 20:12:18]

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, 2016-07-05 21:28:44]

Description was changed from

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org
==========

to

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org
==========

[commit-bot: I haz the power, 2016-07-05 21:28:45]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-05 21:28:48]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-05 21:30:26]

Description was changed from

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org
==========

to

==========
Change ASSERT to CHECK in DrawingBuffer::reset for investigation

Changing this assert to a CHECK which will re-introduce crashes
related to bug 542857, but will result in crash reports that
will allow us to understand how the DrawingBuffer got into
a bad state.

CL to be reverted before next branch point.

BUG=542857
TBR=kbr@chromium.org

Committed: https://crrev.com/9cd13f726995393db68768a714049ea7650b9f86
Cr-Commit-Position: refs/heads/master@{#403824}
==========

[commit-bot: I haz the power, 2016-07-05 21:30:28]

Patchset 1 (id:??) landed as
https://crrev.com/9cd13f726995393db68768a714049ea7650b9f86
Cr-Commit-Position: refs/heads/master@{#403824}