Can you share the revision that you're building this from?

It's a ToT build. Sync-ed earlier today at commit 25e8e9a87ba795375862c9a33ae3d9704eebe489.

We are not seeing this issue anymore.

Just sync-ed to c4f0abb4666f3296485e53fd5ede71f161938048, rebuilt Blimp app and engine.
Seeing this crash consistently now:
Run engine locally.
Launch Blimp.
Result: Assignment succeeds, then Blimp crashes.
Stack-trace is the same as above.

Looks like there was an issue with the device.
Is there any follow up required on this bug?

Nope. Not seeing this any more.

Aah, seeing this again today. Synced to 868930a9584029000df4c195dbd6be71ee98c1da, rebuilt Engine and Client. Install Blimp on device and launch it.
Get the crash noted above.

Not sure why this doesn't happen everytime. i.e., it was working OK yesterday, it's back again today.
Rebooted the device, reinstalled the Blimp APK, same result.
This is the Blimp APK command line:

Existing flags (in /data/local/blimp-command-line):
  <deleted>: 'chrome --engine-ip=127.0.0.1 --engine-port=25467 --engine-transport=tcp'

Engine is launched with this command:
DISPLAY="" out-linux/Debug/blimp_engine_app --user-data-dir=/tmp/blimpengine --enable-logging=stderr --enable-logging   --vmodule="blimp*=2" --disable-gpu  --use-remote-compositing --disable-cached-picture-raster   --blimp-client-token-path=<path to blimpengine-token> --use-gl=osmesa

I can repo the crash after loading  cricbuzz.com. But not Client crash, it was Engine that crashes. 

[1:1:0330/170909:FATAL:display_item_list.cc(107)] Check failed: retain_individual_display_items_. 
#0 0x7f30d098654e base::debug::StackTrace::StackTrace()
#1 0x7f30d09e6dcf logging::LogMessage::~LogMessage()
#2 0x7f30d1bd9c29 cc::DisplayItemList::ToProtobuf()
#3 0x7f30d1be5341 cc::RecordingSource::ToProtobuf()
#4 0x7f30d1b234d4 cc::PictureLayer::LayerSpecificPropertiesToProto()
#5 0x7f30d1aed4d4 cc::Layer::ToLayerPropertiesProto()
#6 0x7f30d1b15183 cc::LayerProtoConverter::SerializeLayerProperties()
#7 0x7f30d1d10e52 cc::LayerTreeHost::ToProtobufForCommit()
#8 0x7f30d1dd41e9 cc::RemoteChannelMain::StartCommitOnImpl()
#9 0x7f30d1dc1597 cc::ProxyMain::BeginMainFrame()
#10 0x7f30d1dd3926 cc::RemoteChannelMain::HandleProto()
#11 0x7f30d1dd364f cc::RemoteChannelMain::OnProtoReceived()
#12 0x7f30ce3e1080 content::RenderWidgetCompositor::OnHandleCompositorProto()
#13 0x7f30ce573b0d content::RenderWidget::OnHandleCompositorProto()

haibin@, the bug for this crash is with the PictureImageLayer, crbug/597163. The fix for this is in CQ.

I'll let Tommy take a look at the image decode error, since it might be tied to the WebPDecoder.

Can we still repro the image decode error?

Yes, I got the crash at software_image_decode_controller.cc just now here, sync-ed earlier today.

With extra debug info from https://codereview.chromium.org/1869573002/


[FATAL:software_image_decode_controller.cc(475)] Check failed: result. id[2] src_rect[0,0 500x228] target_size[428x195] filter_quality[3] can_use_original_decode [0] hash [1151724940]

Stack Trace:
  RELADDR   FUNCTION                 FILE:LINE
  00a6403b  ~LogMessage              base/logging.cc:519
  0078eabf  DecodeImageInternal      cc/tiles/software_image_decode_controller.cc:475
  0078e43b  DecodeImage              cc/tiles/software_image_decode_controller.cc:337
  0078ff01  RunOnWorkerThread        cc/tiles/software_image_decode_controller.cc:71
  0076e289  RunTaskWithLockAcquired  cc/raster/single_thread_task_graph_runner.cc:156
  0076e197  Run                      cc/raster/single_thread_task_graph_runner.cc:117
  00a952d9  Run                      base/threading/simple_thread.cc:87
  00a9525d  ThreadMain               base/threading/simple_thread.cc:66
  00a92a25  ThreadFunc               base/threading/platform_thread_posix.cc:70
  000415db  <unknown>                /system/lib/libc.so
  00019235  <unknown>                /system/lib/libc.so


This seems easier to reproduce on an Android One device.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f4334d7c1f87b92397c8572a9c413d13eb135a28

commit f4334d7c1f87b92397c8572a9c413d13eb135a28
Author: vmpstr <vmpstr@chromium.org>
Date: Wed Apr 06 23:42:25 2016

cc: Images: Add more information to image decode controller DCHECKs

This patch adds more information to the image decode controller DCHECKs
in order to be able to diagnose the problems better.

BUG= 597803 
R=nyquist@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1869573002

Cr-Commit-Position: refs/heads/master@{#385575}

[modify] https://crrev.com/f4334d7c1f87b92397c8572a9c413d13eb135a28/cc/tiles/software_image_decode_controller.cc

CL in review: https://codereview.chromium.org/1867093002/

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/384c6056c4e1d0eb347f705c454437ae40e6f7cb

commit 384c6056c4e1d0eb347f705c454437ae40e6f7cb
Author: nyquist <nyquist@chromium.org>
Date: Thu Apr 07 23:07:06 2016

Add support for defaulting to low quality image interpolation.

Currently only Android sets the flag for
WTF_USE_LOW_QUALITY_IMAGE_INTERPOLATION since it has been the only
platform needing it.

When painting images on one platform, and reproducing them
remotely, the painting side must make sure that the receiving side
is able to render them and ensure that there is no mismatch.

This CL declares a new GN arg so that other platforms may optionally
set this flag as well. The new GN arg is
use_low_quality_image_interpolation and it defaults to is_android.

There should be no changes to existing behavior if the flag is not
set.

BUG= 597803 
R=dpranke@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1867093002

Cr-Commit-Position: refs/heads/master@{#385913}

[modify] https://crrev.com/384c6056c4e1d0eb347f705c454437ae40e6f7cb/build/args/blimp_engine.gn
[modify] https://crrev.com/384c6056c4e1d0eb347f705c454437ae40e6f7cb/third_party/WebKit/Source/config.gni
[modify] https://crrev.com/384c6056c4e1d0eb347f705c454437ae40e6f7cb/tools/mb/mb_config.pyl