[Blob] Removed crash on race case blob messages

[Blob] Removed crash on race case blob messages

We have substantial crashes since adding bad_message errors for invalid
blob messages. It looks like there is a pre-existing condition where
blob references are race casing across processes.

While we investigate the issue, we want to remove this crash so it's not
making the situation worse (crashing instead of having a broken blob).

I'm keeping the uuid.empty() condition as a bad message, because that's
definitely an error that shouldn't be happening.

BUG=606065
Committed: https://crrev.com/3f8e7a2ad99e72ed370e17d7258f64dc7acc49fe
Cr-Commit-Position: refs/heads/master@{#389868}

[dmurph, 2016-04-22 22:46:10]

dmurph@chromium.org changed reviewers:
+ kinuko@chromium.org, michaeln@chromium.org

[dmurph, 2016-04-22 22:46:11]

Tiny patch!

I want to disable the crashing of renderers due to the invalid refcount stuff
(see CL description). I want to get this merged into beta too so it's not going
to start crashing stable.

Daniel

[dmurph, 2016-04-22 22:46:46]

Description was changed from

==========
[Blob] Removed crash on race case blob messages

We have substantial crashes since adding bad_message errors for invalid
blob messages. It looks like there is a pre-existing condition where
blob references are race casing across processes.

While we investigate the issue, we want to remove this crash so it's not
making the situation worse (crashing instead of having a broken blob).

BUG=606065
==========

to

==========
[Blob] Removed crash on race case blob messages

We have substantial crashes since adding bad_message errors for invalid
blob messages. It looks like there is a pre-existing condition where
blob references are race casing across processes.

While we investigate the issue, we want to remove this crash so it's not
making the situation worse (crashing instead of having a broken blob).

I'm keeping the uuid.empty() condition as a bad message, because that's
definitely an error that shouldn't be happening.

BUG=606065
==========

[michaeln, 2016-04-25 21:56:12]

lgtm

[kinuko, 2016-04-26 01:29:22]

lgtm.

[dmurph, 2016-04-26 18:30:26]

The CQ bit was checked by dmurph@chromium.org

[commit-bot: I haz the power, 2016-04-26 18:31:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1913343002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1913343002/1

[commit-bot: I haz the power, 2016-04-26 18:44:20]

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

[commit-bot: I haz the power, 2016-04-26 18:44:21]

Try jobs failed on following builders:
  chromeos_amd64-generic_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-...)
  chromeos_x86-generic_chromium_compile_only_ng on tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)

[dmurph, 2016-04-26 19:19:51]

The CQ bit was checked by dmurph@chromium.org

[dmurph, 2016-04-26 19:19:51]

The patchset sent to the CQ was uploaded after l-g-t-m from kinuko@chromium.org,
michaeln@chromium.org
Link to the patchset: https://codereview.chromium.org/1913343002/#ps20001
(title: "whoops, checking url now instead.")

[commit-bot: I haz the power, 2016-04-26 19:20:28]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1913343002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1913343002/20001

[commit-bot: I haz the power, 2016-04-26 20:13:32]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-26 20:14:47]

Description was changed from

==========
[Blob] Removed crash on race case blob messages

We have substantial crashes since adding bad_message errors for invalid
blob messages. It looks like there is a pre-existing condition where
blob references are race casing across processes.

While we investigate the issue, we want to remove this crash so it's not
making the situation worse (crashing instead of having a broken blob).

I'm keeping the uuid.empty() condition as a bad message, because that's
definitely an error that shouldn't be happening.

BUG=606065
==========

to

==========
[Blob] Removed crash on race case blob messages

We have substantial crashes since adding bad_message errors for invalid
blob messages. It looks like there is a pre-existing condition where
blob references are race casing across processes.

While we investigate the issue, we want to remove this crash so it's not
making the situation worse (crashing instead of having a broken blob).

I'm keeping the uuid.empty() condition as a bad message, because that's
definitely an error that shouldn't be happening.

BUG=606065

Committed: https://crrev.com/3f8e7a2ad99e72ed370e17d7258f64dc7acc49fe
Cr-Commit-Position: refs/heads/master@{#389868}
==========

[commit-bot: I haz the power, 2016-04-26 20:14:48]

Patchset 2 (id:??) landed as
https://crrev.com/3f8e7a2ad99e72ed370e17d7258f64dc7acc49fe
Cr-Commit-Position: refs/heads/master@{#389868}