disable assert for now

disable assert for now

BUG=skia:2012

[hal.canary, 2014-01-10 18:46:09]

https://codereview.chromium.org/134493002/diff/1/src/core/SkBitmap.cpp
File src/core/SkBitmap.cpp (right):

https://codereview.chromium.org/134493002/diff/1/src/core/SkBitmap.cpp#newcod...
src/core/SkBitmap.cpp:1055: //
https://code.google.com/p/skia/issues/detail?id=2012
Should we put in some less strict asserts?  info.fWidth, info.fHeight, and
info.fColorType should all match.

[bsalomon, 2014-01-10 19:06:06]

lgtm until we figure out a larger fix (e.g. should we just make a new pixel ref
for the copy rather than memcpying). This seems to raise a bunch of questions
around the semantics of bitmap copying.

[scroggo, 2014-01-10 20:55:53]

On 2014/01/10 19:06:06, bsalomon wrote:
> lgtm until we figure out a larger fix (e.g. should we just make a new pixel
ref
> for the copy rather than memcpying). This seems to raise a bunch of questions
> around the semantics of bitmap copying.

The original CL was reverted, but I have updated
https://codereview.chromium.org/112113005/ to include the fix from this one.

[scroggo, 2014-01-15 17:08:44]

On 2014/01/10 20:55:53, scroggo wrote:
> On 2014/01/10 19:06:06, bsalomon wrote:
> > lgtm until we figure out a larger fix (e.g. should we just make a new pixel
> ref
> > for the copy rather than memcpying). This seems to raise a bunch of
questions
> > around the semantics of bitmap copying.
> 
> The original CL was reverted, but I have updated
> https://codereview.chromium.org/112113005/ to include the fix from this one.

The other CL was relanded, with the changes suggested here. I'll add a summary
of the issue in https://code.google.com/p/skia/issues/detail?id=2012