Re: Crashes inside CFStringDeallocate
Re: Crashes inside CFStringDeallocate
- Subject: Re: Crashes inside CFStringDeallocate
- From: Vojtěch Meluzín <email@hidden>
- Date: Fri, 25 May 2018 23:18:27 +0200
Ok so I got a solution - it's the utf16 indeed. When I use [NSString
stringWithUTF8String] instead, it doesn't crash. Considering it does that
only on 10.10 (and probably older), it seems like OSX malfunction... oh
well... Fortunately no big deal.
Cheers!
Vojtech
www.meldaproduction.com
2018-05-25 22:49 GMT+02:00 Vojtěch Meluzín <email@hidden>:
> Thanks for the reply Ken. I don't really know what Zombies instrument is,
> I'll check. The GetLength returns the number of UTF-16 characters (hence
> half of the buffer length), not including zero terminator.
>
> Cheers!
> Vojtech
>
> 2018-05-25 16:26 GMT+02:00 Ken Thomases <email@hidden>:
>
>> On May 25, 2018, at 5:44 AM, Vojtěch Meluzín <email@hidden>
>> wrote:
>> >
>> > I have received a few cases like the trace below - it always happens in
>> OSX
>> > 10.10 and runModalForWindow and crashes in CFStringDeallocate. Any ideas
>> > what that could be?
>>
>> Have you run your app with the Zombies instrument?
>>
>> > […] NSStrings, which are
>> > probably the issue here are always created from our MString like this:
>> >
>> > const unichar *utf16 = (const unichar *)s.GetUTF16();
>> > return [NSString stringWithCharacters: utf16 length: s.GetLength()];
>>
>> Does MString::GetLength() return the length in UTF-16 code units (as
>> opposed to, say, UTF-8 code units)?
>>
>> Regards,
>> Ken
>>
>>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden