-
Notifications
You must be signed in to change notification settings - Fork 27
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
Refactor asserts #1
Comments
artyom-razinov
added a commit
that referenced
this issue
Sep 18, 2018
…o to master * commit '2177846fde98475e9e9608a261375abde5bdb201': Move Mixbox to a separate repo
Done |
artyom-razinov
added a commit
that referenced
this issue
May 19, 2020
The problem was probably in bridging, it was crashing at accessing pointers `classList[i]`: Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) #0 0x00007fff23ed2165 in ___forwarding___.cold.3 () #1 0x00007fff23e3e91a in ___forwarding___ () #2 0x00007fff23e40bf8 in __forwarding_prep_0___ () I don't know exactly why current code works, but it does.
artyom-razinov
added a commit
that referenced
this issue
May 19, 2020
The problem was probably in bridging, it was crashing at accessing pointers `classList[i]`: Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) #0 0x00007fff23ed2165 in ___forwarding___.cold.3 () #1 0x00007fff23e3e91a in ___forwarding___ () #2 0x00007fff23e40bf8 in __forwarding_prep_0___ () I don't know exactly why current code works, but it does.
artyom-razinov
added a commit
that referenced
this issue
May 19, 2020
The problem was probably in bridging, it was crashing at accessing pointers `classList[i]`: Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) #0 0x00007fff23ed2165 in ___forwarding___.cold.3 () #1 0x00007fff23e3e91a in ___forwarding___ () #2 0x00007fff23e40bf8 in __forwarding_prep_0___ () I don't know exactly why current code works, but it does.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: