Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KSCrashAblyFork ksthread_getQueueName #846

Closed
tlextrait opened this issue Apr 27, 2019 · 5 comments

Comments

@tlextrait
Copy link

commented Apr 27, 2019

Which version of the Ably SDK are you using?

1.1.3

On which platform does the issue happen?

iOS12

Are you using Cocoapods?

1.6.1

Which version of Xcode are you using?

10.2.1 (10E1001)

What did you do?

Can't reproduce but my users are experiencing it once in a while. This seems to happen when the Ably client is first initialized, or when it first connects. However this only happens once in a while.

SIGSEV
Crashed: Thread
0  KSCrashAblyFork                0x101130290 ksthread_getQueueName + 128
1  KSCrashAblyFork                0x101109a74 monitorCachedData + 276
2  libsystem_pthread.dylib        0x21bd6425c _pthread_body + 128
3  libsystem_pthread.dylib        0x21bd641bc _pthread_start + 48
4  libsystem_pthread.dylib        0x21bd67cf4 thread_start + 4
@ricardopereira

This comment has been minimized.

Copy link
Collaborator

commented May 2, 2019

@tlextrait Thanks for the issue. We will have a look.

@mattheworiordan mattheworiordan added the bug label May 15, 2019

@mattheworiordan

This comment has been minimized.

Copy link
Member

commented May 15, 2019

@ricardopereira do we have any update on this?

@ricardopereira

This comment has been minimized.

Copy link
Collaborator

commented May 16, 2019

@mattheworiordan Unfortunately the stack trace doesn't say much 😕 It seems a bug in the KSKrash dependency so I'll probably update our fork with the latest stable upstream version.

@ricardopereira

This comment has been minimized.

Copy link
Collaborator

commented May 16, 2019

Sorry, I hit the "Close and comment" button 🤦‍♂️

@ricardopereira

This comment has been minimized.

Copy link
Collaborator

commented Jun 11, 2019

Fixed with #858 (comment). It will be released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.