Issue metadata
Sign in to add a comment
|
Push notifications from simple-push-demo.appspot.com are broken on tip of tree |
||||||||||||||||||||||||
Issue descriptionVersion: 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)
,
Apr 4 2016
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?
,
Apr 4 2016
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.
,
Apr 4 2016
This is a duplicate of Issue 599434 , let's continue discussing there. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dominickn@chromium.org
, Apr 4 2016160 KB
160 KB View Download