Play Store Pre Launch report Pixel error
Reported by
car...@instantbits.com,
Jun 16 2017
|
|||||
Issue description
THIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE!
Device name: Pixel XL
Android version: O
WebView version (from system settings -> Apps -> Android System WebView): Don't know
Application: Web Video Caster
Application version: multiple
Every time I release a new apk I get a crash report from the pre launch test and it is always on the Pixel test device and the crash is always this:
* * * * * * * * * * * * * * * *
Build fingerprint: 'google/sailfish/sailfish:O/OPP1.170223.012/3793265:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 15393, tid: 15393, name: myclass >>> mypackage <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
x0 0000000000000000 x1 0000000000000000 x2 0000000000000001 x3 000000000000003f
x4 0000000000000001 x5 00000077a3f2a639 x6 0000000000000003 x7 0000000000000000
x8 bf4eb546325d523c x9 bf4eb546325d523c x10 0000000000430000 x11 bf4eb546325d523c
x12 bf4eb546325d523c x13 0000000000000000 x14 00000077a51107c0 x15 0000000000000000
x16 0000007ff52b6ed0 x17 000000778b054000 x18 0000000000000020 x19 0000007791907d98
x20 0000007776f28804 x21 0000000014906168 x22 0000007ff52b71f0 x23 00000077a3f2a639
x24 0000000000000004 x25 00000077a52c5a98 x26 0000000000000000 x27 0000000000000000
x28 0000000000000001 x29 0000007ff52b6e70 x30 000000778f0845c4
sp 0000007ff52b6e70 pc 000000778f0845c4 pstate 0000000040000000
backtrace:
#00 pc 000000000143d5c4 /system/app/Chrome/Chrome.apk (offset 0x117d000)
I have tested my app on Android O on a 6P and can not reproduce the issue.
,
Jun 16 2017
Oh, so you don't have access to the actual devices? We might have to file this bug against the Play Console team.
,
Jun 16 2017
,
Jun 16 2017
Yeah I don't have access but I might have more logs because they do provide the adb logs. I'll check in a bit. I did make another release a few hours ago and it didn't have that failure so maybe they've already fixed it.
,
Jun 16 2017
Thank you for providing more feedback. Adding requester "gsennton@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 16 2017
Alright, yeah, if you could provide the adb logs that would be very helpful.
,
Jun 16 2017
Let me know if you need more. Log attached.
,
Jun 16 2017
Thanks! That was what I was looking for, the MICRODUMP in there symbolizes to only two lines: 1. libmonochrome.so!Java_org_chromium_content_browser_ContentViewStatics_nativeSetWebKitSharedTimersSuspended 2. system@app@Chrome@Chrome.apk@classes.dex
,
Jun 16 2017
Woops, missed the line number for the first line: libmonochrome.so!Java_org_chromium_content_browser_ContentViewStatics_nativeSetWebKitSharedTimersSuspended [content_view_statics.cc : 76 + 0x0] This points to https://chromium.googlesource.com/chromium/src/+/57.0.2987.35/content/browser/android/content_view_statics.cc The line number 76 is in the following function: 70 void ResumeWebkitSharedTimers() { 71 for (std::vector<int>::const_iterator it = suspended_processes_.begin(); 72 it != suspended_processes_.end(); ++it) { 73 content::RenderProcessHost* host = 74 content::RenderProcessHost::FromID(*it); 75 DCHECK(host); 76 host->RemoveObserver(this); 77 host->GetRendererInterface()->SetWebKitSharedTimersSuspended(false); 78 } 79 suspended_processes_.clear(); 80 }
,
Jun 16 2017
I would imagine that we should get several stack frames here though - not just nativeSetWebKitSharedTimersSuspended, Toby, do you know why we don't get a specific stack frame for the call to ResumeWebkitSharedTimers()?
,
Jun 16 2017
(this is M57 btw) Actually, this looks like a dupe of crbug.com/652489 Carlos, if you don't see this anymore, I'm just gonna dupe this against the bug above. If you still see this issue we should ask Play Console to update their WebView versions (it should be 58 rather than 57 on O anyway).
,
Jun 16 2017
,
Jun 16 2017
I think maybe just some of the test devices don't have the latest because I've had at least one release go by without issue however I just had another release give me the same crash. Anyways, I guess I'll wait. Thank you.
,
Jun 16 2017
I filed an internal bug (b/62699561) against the Play Console, you probably can't access that though :/
,
Jun 16 2017
OPP1 is an outdated preview build of O; I'd just ignore the results here, it won't get newer webview versions. Current preview build starts with OPP3.
,
Jun 16 2017
Thank you. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by gsennton@chromium.org
, Jun 16 2017