Revert of Extract most of the mutable state of SkShader into a separate Context object.

Revert of Extract most of the mutable state of SkShader into a separate Context object. (https://codereview.chromium.org/207683004/)

Reason for revert:
This is blocking the DEPS roll into Chromium. Failures can be seen here:

http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/174333

Original issue's description:
> Extract most of the mutable state of SkShader into a separate Context object.
> 
> SkShader currently stores some state during draw calls via setContext(...).
> Move that mutable state into a separate SkShader::Context class that is
> constructed on demand for the duration of the draw.
> 
> Calls to setContext() are replaced with createContext() which returns a context
> corresponding to the shader object or NULL if the parameters to createContext
> are invalid.
> 
> TEST=out/Debug/dm
> BUG=skia:1976
> 
> Committed: http://code.google.com/p/skia/source/detail?r=14216
> 
> Committed: http://code.google.com/p/skia/source/detail?r=14323

TBR=scroggo@google.com,skyostil@chromium.org,tomhudson@chromium.org,senorblanco@chromium.org,reed@google.com,bungeman@google.com,dominikg@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=skia:1976
Committed: http://code.google.com/p/skia/source/detail?r=14326

[bsalomon, 2014-04-23 16:16:19]

Created Revert of Extract most of the mutable state of SkShader into a separate
Context object.

[commit-bot: I haz the power, 2014-04-23 16:16:28]

CQ is trying da patch. Follow status at
https://skia-tree-status.appspot.com/cq/bsalomon@google.com/249643002/1

[commit-bot: I haz the power, 2014-04-23 16:17:58]

Change committed as 14326

[Dominik Grewe, 2014-04-23 16:18:55]

On 2014/04/23 16:16:28, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
> https://skia-tree-status.appspot.com/cq/bsalomon@google.com/249643002/1

We're aware of this and pointed it out on the original CL (I think Leon added
you to that). There's a very simple fix that we hoped we could land together
with the DEPS roll. We planned that last week but then had to revert due to a
memory leak.

[Dominik Grewe, 2014-04-23 16:20:48]

On 2014/04/23 16:18:55, Dominik Grewe wrote:
> On 2014/04/23 16:16:28, I haz the power (commit-bot) wrote:
> > CQ is trying da patch. Follow status at
> > https://skia-tree-status.appspot.com/cq/bsalomon@google.com/249643002/1
> 
> We're aware of this and pointed it out on the original CL (I think Leon added
> you to that). There's a very simple fix that we hoped we could land together
> with the DEPS roll. We planned that last week but then had to revert due to a
> memory leak.

This would be the fix:
https://codereview.chromium.org/240173003/diff/40001/skia/ext/pixel_ref_utils...

Do you think we can land again and then you include the fix in the roll? That
would make things a lot simpler than staging the CL.

[bsalomon, 2014-04-23 19:07:36]

On 2014/04/23 16:18:55, Dominik Grewe wrote:
> On 2014/04/23 16:16:28, I haz the power (commit-bot) wrote:
> > CQ is trying da patch. Follow status at
> > https://skia-tree-status.appspot.com/cq/bsalomon@google.com/249643002/1
> 
> We're aware of this and pointed it out on the original CL (I think Leon added
> you to that). There's a very simple fix that we hoped we could land together
> with the DEPS roll. We planned that last week but then had to revert due to a
> memory leak.

Sorry for the quick revert. There were multiple problems with the DEPS roll
today and I lost almost the whole day to dealing with it and have kept the Skia
tree closed. In the future it'd be nice to have a flashier way of informing the
sheriff than a CC on a bug with a lot comments. Hopefully, we can automate the
process of including Chromium changes into auto-generated DEPS rolls but until
then non-staged changes incur a high cost. In the end I rolled to a CL before
this revert and included the Chromium side patch. I'm going to revert the
revert.

[bsalomon, 2014-04-23 19:09:15]

A revert of this CL has been created in
https://codereview.chromium.org/246403013/ by bsalomon@google.com.

The reason for reverting is: Chromium side change landed along side DEPS roll
that includes r14323..

[Dominik Grewe, 2014-04-23 20:23:06]

On 2014/04/23 19:07:36, bsalomon wrote:
> On 2014/04/23 16:18:55, Dominik Grewe wrote:
> > On 2014/04/23 16:16:28, I haz the power (commit-bot) wrote:
> > > CQ is trying da patch. Follow status at
> > > https://skia-tree-status.appspot.com/cq/bsalomon@google.com/249643002/1
> > 
> > We're aware of this and pointed it out on the original CL (I think Leon
added
> > you to that). There's a very simple fix that we hoped we could land together
> > with the DEPS roll. We planned that last week but then had to revert due to
a
> > memory leak.
> 
> Sorry for the quick revert. There were multiple problems with the DEPS roll
> today and I lost almost the whole day to dealing with it and have kept the
Skia
> tree closed. In the future it'd be nice to have a flashier way of informing
the
> sheriff than a CC on a bug with a lot comments. Hopefully, we can automate the
> process of including Chromium changes into auto-generated DEPS rolls but until
> then non-staged changes incur a high cost. In the end I rolled to a CL before
> this revert and included the Chromium side patch. I'm going to revert the
> revert.

Thanks!