Chrome Version: Tip of master
OS: Android (KitKat only)

What steps will reproduce the problem?
(1) Run CaptureScreenshotTest.CaptureScreenshotJpeg on a Kindle Fire HDX 8.9 (3rd Generation)

What is the expected result?
The test passes

What happens instead?
C  122.117s Main  ********************************************************************************
C  122.118s Main  [UNKNOWN] CaptureScreenshotTest.CaptureScreenshotJpeg:
C  122.118s Main  [ RUN      ] CaptureScreenshotTest.CaptureScreenshotJpeg
C  122.118s Main  [ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,0): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,1): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,2): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,3): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,4): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,5): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,6): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,7): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,8): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(595)] Pixel (0,9): expected 4279383126 actual 4278190080
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(605)] Number of pixel with an error: 1131200
C  122.118s Main  [ERROR:devtools_protocol_browsertest.cc(606)] Error Bounding Box : 0,0 1600x707
C  122.118s Main  ../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:647: Failure
C  122.118s Main  Value of: MatchesBitmap(expected_bitmap, *result_bitmap, matching_mask, error_limit)
C  122.118s Main    Actual: false
C  122.118s Main  Expected: true
C  122.118s Main  [  FAILED  ] CaptureScreenshotTest.CaptureScreenshotJpeg, where TypeParam =  and GetParam() =  (2774 ms)
C  122.118s Main  [----------] 1 test from CaptureScreenshotTest (2774 ms total)
C  122.118s Main  
C  122.118s Main  [----------] Global test environment tear-down
C  122.118s Main  [==========] 1 test from 1 test case ran. (2776 ms total)
C  122.118s Main  [  PASSED  ] 0 tests.
C  122.118s Main  [  FAILED  ] 1 test, listed below:
C  122.118s Main  [  FAILED  ] CaptureScreenshotTest.CaptureScreenshotJpeg, where TypeParam =  and GetParam() = 
C  122.119s Main  
C  122.119s Main   1 FAILED TEST
C  122.119s Main  <<ScopedMainEntryLogger
C  122.119s Main  ********************************************************************************
C  122.119s Main  Summary
C  122.119s Main  ********************************************************************************
C  122.119s Main  [==========] 1 test ran.
C  122.119s Main  [  PASSED  ] 0 tests.
C  122.119s Main  [  FAILED  ] 1 test, listed below:
C  122.119s Main  [  FAILED  ] CaptureScreenshotTest.CaptureScreenshotJpeg (UNKNOWN)
C  122.119s Main  
C  122.119s Main  1 FAILED TEST
C  122.119s Main  ********************************************************************************

Please use labels and text to provide additional information.
Lots of incorrect pixels - something's going fundamentally wrong. I've tried increasing "error_limit" or using the Mac solution, but neither make a significant difference.
The same test passes on Lollipop on a virtually identical device. (4th Gen HDX 8.9)