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

Issue 600247 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 599434
Owner:
no longer working on chrome
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Push notifications from simple-push-demo.appspot.com are broken on tip of tree

Project Member Reported by dominickn@chromium.org, Apr 4 2016

Issue description

Version: 51.0.2700 (tip of tree)
OS: Android

What steps will reproduce the problem?
(1) visit https://simple-push-demo.appspot.com
(2) enable push notifications and accept the prompt
(3) push the button to send a XHR notification via GCM

What is the expected output?

A notification is sent to the device.

What do you see instead?

Chromium crashes, with the attached tombstone indicating some sort of JNI string check error in GCM.

This was reproduced on four separate Nexus devices. The problem doesn't exist on the current Chrome dev on Android (51.0.2693.2)
 
tombstone.txt attached.
tombstone2.txt
160 KB View Download
Components: Blink>PushAPI
Owner: joh...@chromium.org
Status: Assigned (was: Untriaged)
I wonder how we got from nativeOnMessageReceived to TopSitesDatabase, that does not seem to be related.

John, could you take a look please as it is GCM?
The TopSitesDatabase seems to just be stack corruption. Looks like the sender ID might be null, causing a DCHECK to fail in ConvertJavaStringToUTF8(env, j_sender_id) called from GCMDriverAndroid::OnMessageReceived.

Unclear if anything bad would happen in release builds, but we shouldn't be getting null sender IDs from GCM. I'll try to reproduce.

Comment 4 by peter@chromium.org, Apr 4 2016

Mergedinto: 599434
Status: Duplicate (was: Assigned)
This is a duplicate of  Issue 599434 , let's continue discussing there.

Sign in to add a comment