OOP PDF - Allow OOP PDF to use histograms

OOP PDF - Allow OOP PDF to use histograms

This patch adds libpdf.so to whitelisted plugins so that
it can use histograms. Without this patch, an error is
displayed every time when Chrome is launched with OOP PDF flag
and PDF file is opened.

BUG=405305
Committed: https://crrev.com/3c922e3f2152399787cdf8f800c5c7f71af78308
Cr-Commit-Position: refs/heads/master@{#292109}

[Nikhil, 2014-08-26 08:37:22]

n.bansal@samsung.com changed reviewers:
+ raymes@chromium.org

[Nikhil, 2014-08-26 08:37:38]

n.bansal@samsung.com changed reviewers:
+ thestig@chromium.org

[Nikhil, 2014-08-26 08:39:37]

PTAL at my proposed solution to fix histogram related error that is shown every
time Chrome is launched with --out-of-process-pdf and a pdf file is opened.

Thanks!

[raymes, 2014-08-27 01:03:47]

lgtm - as long as you have tested that it actually fixes the bug :)

[Nikhil, 2014-08-27 05:32:22]

On 2014/08/27 01:03:47, raymes wrote:
> lgtm - as long as you have tested that it actually fixes the bug :)

Yes, this definitely fixes the error "Host or histogram name is not allowed to
use the UMA API" that we get every time we use OOP and open pdf file. I've
tested that. But, it needs to be checked whether reporting works fine with this
or not (I don't have access). Please see -
https://code.google.com/p/chromium/issues/detail?id=390315

Please let me know if I should go ahead and land this.

[raymes, 2014-08-27 05:41:43]

On 2014/08/27 05:32:22, Nikhil wrote:
> On 2014/08/27 01:03:47, raymes wrote:
> > lgtm - as long as you have tested that it actually fixes the bug :)
> 
> Yes, this definitely fixes the error "Host or histogram name is not allowed to
> use the UMA API" that we get every time we use OOP and open pdf file. I've
> tested that. But, it needs to be checked whether reporting works fine with
this
> or not (I don't have access). Please see -
> https://code.google.com/p/chromium/issues/detail?id=390315
> 
> Please let me know if I should go ahead and land this.

Sure please go ahead and land it :)

[Nikhil, 2014-08-27 05:42:39]

The CQ bit was checked by n.bansal@samsung.com

[commit-bot: I haz the power, 2014-08-27 05:43:33]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/n.bansal@samsung.com/508543002/1

[commit-bot: I haz the power, 2014-08-27 06:51:11]

Committed patchset #1 (1) as d3eb517e681bda3623b24ca485066191bac8e279

[commit-bot: I haz the power, 2014-09-10 02:50:12]

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