cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Trott (JIRA)" <>
Subject [jira] [Updated] (CB-5132) Certain Types Of Async Activity + ClickBusting + Cordova + Android Galaxy S4 = unexpected exit
Date Sun, 20 Oct 2013 06:17:43 GMT


Rich Trott updated CB-5132:

    Attachment: s4-angular-cordova-bug.tgz

Gzipped tar file containing the cordova project demonstrating this bug.

> Certain Types Of Async Activity + ClickBusting + Cordova + Android Galaxy S4 = unexpected
> ----------------------------------------------------------------------------------------------
>                 Key: CB-5132
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 3.1.0
>         Environment: Galaxy S4 running Android 4.2.2. I've been unable to replicate the
bug on emulators. The bug only shows up on actual devices. Fortunately, Samsung makes them
available via
>            Reporter: Rich Trott
>         Attachments: s4-angular-cordova-bug.tgz
> I created a repo with more-or-less minimal code to demonstrate the issue:
> The app in the repo exits (in a "oh, hey, I crashed, I'm outta here!" kind of way) when
run on a Galaxy S4 running Android 4.2.2. It runs fine on every other device I've tested it
on. For example, there is no problem on a Galaxy Note II running Android 4.1.2. 
> The www directory stuff also works fine in browsers, including browsers on the S4/Android
4.2.2 device.
> So the bug only seems to happen when this code is:
> * Run as a Cordova app
> * On a Galaxy S4 running Android 4.2.2
> Steps to duplicate the behavior (which are also listed in the repo's README) are:
> 1. Clone the 
> 2. Create the Android executable using Cordova. With `cordova` command line tool and
Android SDK installed: 
>   - `cordova platform add android`
>   - `cordova build`
> 3. Take the resulting APK and install it on a Galaxy S4 running Android 4.2.2. If you
don't own one, you can test with one for free at
> 4. Launch the app.
> 5. Touch the text on the app's main screen.
> 6. Wait a few seconds and the app will exit.
> On everything else I've tested, it loads the color list content, which is the expected
> This shows up in the Android logs, at least when using
>     ERROR|10-19 03:39:49.448|6938|6938||CallbackProxy|UPDATE_URL
>     ASSERT|10-19 03:39:49.493|6938|6953||libc|Fatal signal 11 (SIGSEGV) at 0x00000000
(code=1), thread 6953 (WebViewCoreThre)
> I put this information in a question on StackOverflow (
It has attracted some helpful comments from one individual, but so far that's it.

This message was sent by Atlassian JIRA

View raw message