Instruments reports leaks in NSRegularExpression Class

Solar2D General Questions/Discussion
#1

Running our Corona app with Instruments, I instantly get dozens of small memory leaks in Leaked Object icu::UVector64 and icu:RegexMatcher, with Responsible Frame in the NSRegularExpression class (mostly initWithPattern).

Is it related to something wrong with my code, or is it a problem with the Corona core?

Will this be fixed in coming builds? (Let me know if I should send log data of any kind)

Will it cause submission problems?

#2

I’ve never heard of this being an issue but perhaps you are regexing with more vigor than other apps.  Please file a bug with a minimal reproducible case. 

EDIT: string matching in Lua is not regular expression based and does not use NSRegularExpression

#3

I’ve never heard of this being an issue but perhaps you are regexing with more vigor than other apps.  Please file a bug with a minimal reproducible case. 

EDIT: string matching in Lua is not regular expression based and does not use NSRegularExpression

#4

Any update on this issue? I have the same problem - I get leaks in icu::RegexPattern in NSRegularExpression initWithPattern:options:error. 

All I am using regular expressions for is two simple string.match calls:

local a = string.match(t.name, "%a+") local n = tonumber(string.match(t.name, "%d+"))
#5

You don’t need to worry about these leaks (they represent a tiny amount of memory in the grand scheme of things and don’t grow much over the course of an app session).  They are not caused by string matching in Lua as that does not use any iOS code (mostly because string matching in Lua is not regular expression based though there are similarities).

In debugging these it’s unclear where these come from as they aren’t tracible back to Corona SDK code.

#6

Any update on this issue? I have the same problem - I get leaks in icu::RegexPattern in NSRegularExpression initWithPattern:options:error. 

All I am using regular expressions for is two simple string.match calls:

local a = string.match(t.name, "%a+") local n = tonumber(string.match(t.name, "%d+"))
#7

You don’t need to worry about these leaks (they represent a tiny amount of memory in the grand scheme of things and don’t grow much over the course of an app session).  They are not caused by string matching in Lua as that does not use any iOS code (mostly because string matching in Lua is not regular expression based though there are similarities).

In debugging these it’s unclear where these come from as they aren’t tracible back to Corona SDK code.