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 KERN_INVALID_ADDRESS 0x0000000000000010 #4408

Closed
amplework opened this issue Mar 14, 2022 · 5 comments
Closed

EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000010 #4408

amplework opened this issue Mar 14, 2022 · 5 comments

Comments

@amplework
Copy link

amplework commented Mar 14, 2022

How frequently does the bug occur?

Sometimes

Description

I have 23 crashes in production precisely like this from 12 different users.

image

Stacktrace & log output

No response

Can you reproduce the bug?

Not yet

Reproduction Steps

No response

Version

10.10.1

What SDK flavour are you using?

Local Database only

Are you using encryption?

No, not using encryption

Platform OS and version(s)

ios

Build environment

Which debugger for React Native: ..

Cocoapods version

1.11.2

@fronck
Copy link

fronck commented Mar 16, 2022

@amplework Thanks for reporting this issue.
Would you be able to share the schema you're working with when this crash happens?

@fronck fronck added the More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. label Mar 16, 2022
@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label Mar 16, 2022
@amplework
Copy link
Author

@fronck i have added my schema below:

export const CURRENT = 'Current';
export const WORKOUTLIST = 'WorkoutList';
export const USER_WORKOUT_INFO = 'UserWorkoutInfo';
export const PROGRAM = 'Program'

export const CurrentSchema = {
name: CURRENT,
primaryKey: 'id',
properties:{
id: 'string?',// DeviceInfo.getUniqueId(),
memberships: 'Membership?',
program: 'Program?',
workout: 'Workout?',
team: 'Team?',
workoutList: 'WorkoutList[]',
programs: 'Program[]',
userWorkoutInfo: 'UserWorkoutInfo?'
}
};

export const WorkoutListSchema = {
name: WORKOUTLIST,
embedded: true,
properties: {
name: 'string?',
published: 'bool?',
_id: 'string?',
}
};

export const UserWorkoutInfoSchema = {
name: USER_WORKOUT_INFO,
embedded: true,
properties: {
created: 'date?',
currentDay: 'int?',
supplementDay: 'int?',
updated: 'date?',
_currentProgram: 'string?',
_currentTeam: 'string?',
_currentWorkout: 'string?',
_id: 'string?',
_lastWorkout: 'string?',
_secondLastWorkout: 'string?',
_supplementProgram: 'string?',
_supplementTeam: 'string?',
_supplementWorkout: 'string?',
_user: 'string?',
isPendingSync: 'bool?'
}
};

@no-response no-response bot removed the More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. label Mar 17, 2022
@github-actions github-actions bot added Needs-Attention Reporter has responded. Review comment. and removed Waiting-For-Reporter Waiting for more information from the reporter before we can proceed labels Mar 17, 2022
@fronck
Copy link

fronck commented Mar 17, 2022

@amplework Thanks for that.
Do you have any idea what the users are doing at the time of the crash (e.g., inserting/deleting Workouts or Programs, initializing the DB)?

Also, does your screenshot above include the entire stacktrace? It seems like it may have gotten cut off at the bottom.

@amplework
Copy link
Author

@fronck user is initialized Workouts or Programs in DB.

I have added full screenshot of crashes below:

image
image
image
image

@sync-by-unito sync-by-unito bot removed the Needs-Attention Reporter has responded. Review comment. label Mar 22, 2022
@kneth
Copy link
Contributor

kneth commented Sep 1, 2022

We have been reworking the interaction with JavaScriptCore by using the new JSI api. Please upgrade to v11.0.0-rc.1. If you still experience the issue after upgrading, please either reopen the issue or create a new issue.

@sync-by-unito sync-by-unito bot closed this as completed Sep 1, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants