[Android] Fix crashes on Chrome internal pages.

[Android] Fix crashes on Chrome internal pages.

CompositorViewHolder#mControlContainer can be null on viewing internal
pages, so check it before using it.

Also fixed progress bar API calling order in
LoadProgressSimulator.

BUG=514955
Committed: https://crrev.com/1bde929fcf8b4ec353b3b9818256910f6dcad426
Cr-Commit-Position: refs/heads/master@{#341198}

[Kibeom Kim (inactive), 2015-07-30 06:05:56]

The CQ bit was checked by kkimlabs@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-30 06:06:16]

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

[Kibeom Kim (inactive), 2015-07-30 06:08:57]

The CQ bit was checked by kkimlabs@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-30 06:09:19]

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

[Kibeom Kim (inactive), 2015-07-30 06:10:39]

kkimlabs@chromium.org changed reviewers:
+ dtrainor@chromium.org, tedchoc@chromium.org

[commit-bot: I haz the power, 2015-07-30 07:17:57]

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

[commit-bot: I haz the power, 2015-07-30 07:17:57]

Dry run: This issue passed the CQ dry run.

[Ted C, 2015-07-30 15:02:13]

https://codereview.chromium.org/1264813002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/compositor/CompositorViewHolder.java
(right):

https://codereview.chromium.org/1264813002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/compositor/CompositorViewHolder.java:548:
mProgressBarDrawingInfo = null;
why do you need to set it to null here?

does the drawing code handle it if we go from non-null to null?  Does null clear
out the progress bar or would it leave it drawing the old state?

[Kibeom Kim (inactive), 2015-07-30 17:00:28]

https://codereview.chromium.org/1264813002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/compositor/CompositorViewHolder.java
(right):

https://codereview.chromium.org/1264813002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/compositor/CompositorViewHolder.java:548:
mProgressBarDrawingInfo = null;
On 2015/07/30 15:02:13, Ted C wrote:
> why do you need to set it to null here?
> 
> does the drawing code handle it if we go from non-null to null?  Does null
clear
> out the progress bar or would it leave it drawing the old state?

Done.

(Changed to assert since we expect mControlContainer to be initialized only
once, but I can also change to handle clearing)

[David Trainor- moved to gerrit, 2015-07-30 20:54:34]

lgtm

[Kibeom Kim (inactive), 2015-07-30 20:55:57]

Ted: I'll land as it is for now as this is a Dev blocker, but I'll address in a
later CL if you have comments.

[Kibeom Kim (inactive), 2015-07-30 20:56:02]

The CQ bit was checked by kkimlabs@chromium.org

[commit-bot: I haz the power, 2015-07-30 20:57:35]

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

[commit-bot: I haz the power, 2015-07-30 21:37:39]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-07-30 21:38:21]

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