New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 775871 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

webview crash when playing video using youtube iframe api

Reported by joahae7...@gmail.com, Oct 18 2017

Issue description

Steps to reproduce the problem:
when playing video using Youtube IFrame API I have been experiencing memory crashes (webview v61.0.3163.98.)

What is the expected behavior?
The terminal information is as follows.

 -. Model Name : SM-G900F(S5)
 -. Android OS : 5.0
 -. RAM : 2GB

What went wrong?
Attach the dump log

Did this work before? No 

Chrome version: v61.0.3163.98.  Channel: dev
OS Version: 5.0
Flash Version: 

This is probably caused by terminal memory stick.
 
youtube_webview crash_Logcat.txt
4.9 MB View Download
Cc: msrchandra@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org ligim...@chromium.org sandeepkumars@chromium.org
Labels: Needs-triage-Mobile TE-NeedsTriageFromMTV
Could some one from MTV Team, please look into the issue as it is related to memory stick.
Thank You.
Components: -Blink Mobile>WebView
This microdump won't symbolize by default because the webview binary GUID is missing.
I downloaded the appropriate binary with:

clank/bin/report_disassembly.py -A arm -V 61.0.3163.98 -P AndroidWebview -w /tmp/objdump -N

and then got the ID with:

dump_syms -i /tmp/objdump/AndroidWebview-61.0.3163.98-arm.so

MODULE Linux arm A06EB4D41B719D929B3EF8B7F5E32FB20 AndroidWebview-61.0.3163.98-arm.so
INFO CODE_ID D4B46EA0711B929D9B3EF8B7F5E32FB2FFFAB9FE

Inserting A06EB4D41B719D929B3EF8B7F5E32FB20 into the microdump at the right place gives the following symbolization, which is pretty clearly an OOM.

 0  libwebviewchromium.so!WTF::PartitionsOutOfMemoryUsing32M() [Partitions.cpp : 190 + 0x6]
     r0 = 0x000000be    r1 = 0x01cf2000    r2 = 0x00629000    r3 = 0x000b2000
     r4 = 0x00000000    r5 = 0x003b6000    r6 = 0x00000000    r7 = 0xa530e2bc
     r8 = 0x003bb000    r9 = 0x003b6000   r10 = 0x003b6000   r12 = 0xa5301af4
     fp = 0xa5316fc0    sp = 0x69195828    lr = 0xa365c9a7    pc = 0xa365c9ac
    Found by: given as instruction pointer in context
 1  libwebviewchromium.so!WTF::Partitions::HandleOutOfMemory() [Partitions.cpp : 224 + 0x3]
     r4 = 0x00000000    r5 = 0x003b6000    r6 = 0x00000000    r7 = 0x0defaced
     r8 = 0x003bb000    r9 = 0x003b6000   r10 = 0x003b6000    fp = 0xa5316fc0
     sp = 0x69195838    pc = 0xa365c785
    Found by: call frame info
 2  libwebviewchromium.so!base::PartitionOutOfMemory(base::PartitionRootBase const*) [partition_alloc.cc : 266 + 0x3]
     r4 = 0x00000000    r5 = 0x003b6000    r6 = 0x00000000    r7 = 0x0defaced
     r8 = 0x003bb000    r9 = 0x003b6000   r10 = 0x003b6000    fp = 0xa5316fc0
     sp = 0x69195848    pc = 0xa2eb9f31
    Found by: call frame info

Looking at the histogram of free memory regions, the largest available memory region is only 64K, so it's hardly surprising.

Comment 6 Deleted

Status: WontFix (was: Unconfirmed)

Sign in to add a comment