-
Notifications
You must be signed in to change notification settings - Fork 584
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 JSC getOwnPropertySlot #2416
Comments
We're seeing similar stacktraces on our app as well:
|
@dkpalmer @rajivshah3 Have you observe these crashes in recent versions? |
We have also observed it in v2.28.1 & RN 0.59 |
@nileshchavan Thanks for the update. We haven't been able to reproduce it. Do you know which situations it is happening? Is it during low memory situations? |
@kneth we haven't been able to reproduce it as well. Based on crash reports, it seems that this is happening during low memory situations. Here are more details about the issue: Environment & crash details:
Besides
|
This probably happens when OS tries to terminate the application and app is trying to free up all resources. I found similar issue in componentKit. facebook/componentkit#892 |
@nileshchavan Thank you for providing a link. |
Hi, we have similar problem with results listeners. I'm wondering if there is a way to solve it? Results listeners are good mechanism which we want to use |
@KowalskiP Can you reproduce the crash in a simple app? It could help us understand what the cause is. |
Having the same issue in 5.0.3 |
We have recently rewritten how we interact with JavaScriptCore (JSC) by using the new JSI api. I am closing this issue by suggesting you try v11.0.0-rc.1 or later. |
tl;dr I'm hoping the included stack traces below might shed some light on what could be causing some
EXC_BAD_ACCESS
crashes from the JSC and Realm.--
Since our latest release we have started getting crashes that all look to have Realm and JSC in the picture:
EXC_BAD_ACCESS Attempted to dereference garbage pointer 0x10.
And usually either from
JSC::JSFunction::getOwnPropertySlot
orJSC::JSCallbackObject<T>::getOwnPropertySlot
called by a Realm function (e.g.get_property_names
,get_property
).Unfortunately, this was a very large release for us so it's hard to know where I could look to try and provide a way to isolate the issue. Realm related in this release, we:
I would appreciate any insights the Realm team can provide. Happy to dig into any ideas or thoughts you all might have.
A few stack traces are included below for reference. All fairly similar but generally the crashes are coming up as unique in Sentry.
Version of Realm and Tooling
The text was updated successfully, but these errors were encountered: