Re: Crashes inside CFStringDeallocate

While your UTF-8 representation works, it would be worth it to verify your data is correct. Whenever I have messes with Unicode, or any data for that matter which can be external to an Xcode execution, I eyeball the actual bytes with Hex Fiend: https://github.com/ridiculousfish/hexfiend

Re: Crashes inside CFStringDeallocate

Hard to say really, but we know that it does work properly on newer OSX (so there is either some sort of compatibility change, classic Apple, or there was a bug). I believe the UTF16 implementation we are using is correct, and it was used in other places in the software as well, and it always worke