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

EXC_BAD_ACCESS #94

Closed
1N50MN14 opened this issue Nov 26, 2015 · 2 comments
Closed

EXC_BAD_ACCESS #94

1N50MN14 opened this issue Nov 26, 2015 · 2 comments

Comments

@1N50MN14
Copy link

I was wondering if anyone has any pointers as to what might cause this:

Process 998 stopped
* thread #8: tid = 0x34807, 0x25c634aa JavaScriptCore`WTFCrash + 54, name = 'WebThread', stop reason = EXC_BAD_ACCESS (code=1, address=0xbbadbeef)
    frame #0: 0x25c634aa JavaScriptCore`WTFCrash + 54
JavaScriptCore`WTFCrash:
->  0x25c634aa <+54>: str    r1, [r0]
    0x25c634ac <+56>: trap
    0x25c634ae <+58>: nop

JavaScriptCore`WTFCrashWithSecurityImplication:
    0x25c634b0 <+0>:  push   {r4, r7, lr}
(lldb)
@ibc
Copy link
Collaborator

ibc commented Nov 26, 2015

There are tons of cases in which that happens, for example when CPU is very busy doing other heavy tasks. Anyhow ensure you are using the provided WebSocket workaround (see #12).

I close this issue because there is no a magic solution/workaround for this.

@ibc ibc closed this as completed Nov 26, 2015
@1N50MN14
Copy link
Author

Right, thanks for the pointer it might just as well be that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants