Blacklists virtualCamera.ax

Blacklists virtualCamera.ax.

Tries to avoid crash in media::CoreAudioUtil::CreateDeviceEnumerator by blacklisting a DLL which accounts for a large amount of crashes we see in CreateDeviceEnumerator.

BUG=383715, 378465
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276946

[henrika (OOO until Aug 14), 2014-06-12 11:18:48]

Tommi, adding one module here (not sure if .ax is OK). Dale suggests two more.
Should we add them as well?

[henrika (OOO until Aug 14), 2014-06-12 11:25:18]

robertshield@: adding you as owner. Thanks!

[tommi (sloooow) - chröme, 2014-06-12 11:28:14]

lgtm

[henrika (OOO until Aug 14), 2014-06-12 11:32:43]

robertshield@: if you are OK, please press the button, thx.

[robertshield, 2014-06-12 23:37:31]

lgtm

FYI csharp@, this is apparently blocking canary release due to high crash rate. 

Approving for now. Please make sure to follow the blacklist process at
http://www.chromium.org/Home/third-party-developers#TOC-Getting-Blacklisted as
well.

[commit-bot: I haz the power, 2014-06-12 23:40:15]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/henrika@chromium.org/325323003/1

[commit-bot: I haz the power, 2014-06-13 06:47:56]

Change committed as 276946

[henrika (OOO until Aug 14), 2014-06-13 07:07:49]

On 2014/06/12 23:37:31, robertshield wrote:
> lgtm
> 
> FYI csharp@, this is apparently blocking canary release due to high crash
rate. 
> 
> Approving for now. Please make sure to follow the blacklist process at
> http://www.chromium.org/Home/third-party-developers#TOC-Getting-Blacklisted as
> well.

robertshield@: I did read the process but it is not clear to me what exactly is
expected from me here. To me it sounds as if any contact with a DLL developer
should go through some more official channel or am I supposed to try to dig up a
contact person and explain we crash etc.?

[csharp, 2014-06-13 12:43:31]

On 2014/06/13 07:07:49, henrika wrote:
> On 2014/06/12 23:37:31, robertshield wrote:
> > lgtm
> > 
> > FYI csharp@, this is apparently blocking canary release due to high crash
> rate. 
> > 
> > Approving for now. Please make sure to follow the blacklist process at
> > http://www.chromium.org/Home/third-party-developers#TOC-Getting-Blacklisted
as
> > well.
> 
> robertshield@: I did read the process but it is not clear to me what exactly
is
> expected from me here. To me it sounds as if any contact with a DLL developer
> should go through some more official channel or am I supposed to try to dig up
a
> contact person and explain we crash etc.?

You should send an announcement email to
chrome-blacklisting-announce@chromium.org to let people know that this is now
blocked, and then if possible you should try and contact the developer (if you
can find them) and let them know what we've blocked and why.

[henrika (OOO until Aug 14), 2014-06-15 13:59:24]

A revert of this CL has been created in
https://codereview.chromium.org/335073002/ by henrika@chromium.org.

The reason for reverting is: No crashes have been found after 37.0.2046.2 and
Canary on Windows is now on 37.0.2051.2, hence it looks good. Not sure if was
the blacklisting or the "calling CoInitializeEx twice" patch which did the trick
here.

I would like to revert the blacklisting patch to see if we can cope with the
CoInitializeEx patch only. It would be great if we could avoid adding another
DLL to the blacklist..