Memory Leaks on iOS TOMLTable.convert(to:options:)

[codingiran]

My Code is quit simple:

// a toml string
var tomlString = '''
port = 6789
socks_port = 7890
allow_lan = false
bind_address = '*'
log_level = 'debug'
ipv6 = false
tun_fd = 0
'''
// `NetspeedConfig` is a Swift Struct define in my app
var config = try TOMLDecoder().decode(NetspeedConfig.self, from: tomlString)

// set property etc.
config.tun_fd = 10
...

// convert to toml string
tomlString = try TOMLEncoder().encode(config)

// create a TOMLKit table
let table = try TOMLTable(string: tomlString)

// convert to strings
let output_toml = table.convert(to: .toml)
let output_json = table.convert(to: .json)
let output_yaml = table.convert(to: .yaml)

Xcode Instruments catch this memory leak, please download it and check in Xcode
https://github.com/codingiran/TOMLKit/blob/main/MemoryLeaks/TOMlKit%20Memory%20Leaks.trace.zip

[nikitabobko]

The library is full of memory leaks. Basically, almost every returned value from cpp to Swift is returned via malloc or cpp new and never freed...

[nikitabobko]

There a few probably trivial memory leak fixes?

• nikitabobko@b2932ca
• nikitabobko@020d5da
• nikitabobko@d988ba0

But the one this issue is about inside TOMLTable.init / tableCreateFromString is slightly more complicated. A simple TOMLTable.deinit cannot be slapped in, because the ownership for tablePointer: OpaquePointer are not immediately trivial to me. The pointer can travel from TOMLTable to TOMLTable.

[xiaowei-dreame]

This makes me worried to use😂

[codingiran]

This makes me worried to use😂

@nikitabobko did fix memory leak, you can try his fork version