cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Grogor (JIRA)" <>
Subject [jira] [Commented] (CB-2301) EXC_BAD_ACCESS on resume/wake on iOS device
Date Mon, 04 Aug 2014 18:16:13 GMT


Francois Grogor commented on CB-2301:

Is this issue still open? I have been following this thread in the hope of a resolution.

I have the exact same symptoms in that my IOS app is crashing on resume. I am using Socket
IO with nodejs.

For now I have put a work around in to disconnect the client socket on pause and reconnect
on resumes. This does however result in a downgraded experience for my users! Is this really
the only option currently?

> EXC_BAD_ACCESS on resume/wake on iOS device
> -------------------------------------------
>                 Key: CB-2301
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.2.0
>         Environment: iPhone 5 running iOS 6.0.2 and Phonegap 2.2.0. (Xcode 4.5.2 on Mountain
>            Reporter: Ross Holdway
>            Assignee: Shazron Abdullah
>            Priority: Critical
>              Labels: cordova, ios, phonegap
>             Fix For: 2.5.0
>         Attachments:, Screenshot.png
> I have implemented a websocket connection (using within my app which it uses
to communicate with the server. On locking and waking the device, it disconnects and reconnects
correctly, but on leaving the device locked for 1 minute or longer when unlocking, the application
will crash sometimes instantly, or sometimes after reconnecting with the server.
> If I do the same, but run my app within mobile Safari, it does not crash, leading me
to believe this is an issue with Phonegap/Cordova. 
> On app crash, within Xcode I get within WebThread - WebCore::ThreadTImers::sharedTimerFiredInternal()
an EXC_BAD_ACCESS (code=1) error
> Screenshot of crash state in Xcode -
> Hopefully someone will have an idea as to what could be causing this, or recommend some
tests for me to run etc because I'm really clueless on how to proceed with fixing this!
> Many Thanks,
> Ross

This message was sent by Atlassian JIRA

View raw message