parseMultiple EXC_BAD_ACCESS about phonenumberkit

[marmelroy]

Thanks @adrianchifor. I'll investigate tonight.

[marmelroy]

Thanks @nrako. Didn't know about this issue. Will investigate...

[nrako]

Thanks @marmelroy

I also have an SIGABRT error sometimes but I have the feeling it's related so I'm reporting it here.

console:

myapp(46653,0x700000d5f000) malloc: *** error for object 0x7f8f4a5b54f0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

Sorry for "screenshooting" this issue 😬 , let me know if I can help in another way.

[adrianchifor]

Happens to me as well. Got the same stacktrace as @nrako

[marmelroy]

Thanks @adrianchifor. Do you have reproducible steps / code I can look at? It will be super useful...

[adrianchifor]

This is where it crashes:

The stacktrace:

[adrianchifor]

@marmelroy Managed to solve this for my project. Turned out that the issue was being caused by passing a string to PhoneNumber.init from a strings array which was passed by reference to my function. The strings array was modified on another thread which caused EXC_BAD_ACCESS because PhoneNumberKit was trying to use a string that was no longer there.

[marmelroy]

Oh, okay. In that case I have a cool generalised solution in mind. Will commit in a few hours.

[marmelroy]

Discovered a few possible issues here. Have a fix that I want to test more before pushing.

[marmelroy]

Should be fixed by 40410c8 (new release soon).

[Jean-Daniel]

This crash is due to concurrent access to the regularExpresionPool in RegexManager.