You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2024. It is now read-only.
There are various places within our Swift library where we're not feeing memory used within Rust correctly or completely, which will cause memory leaks in an application which uses our library. Places we've found so far:
The Util.collectTo method copies memory when converting from Rust vectors to Swift arrays. We should free the underlying memory after copying
When converting strings (Util.rustStringToSwift) from Rust to Swift, we're calling free methods on the underlying Rust types, but we aren't doing anything when we move data from Swift into Rust (Util.rustStringToSwift) which might also need work to free
Look into this comment about strings going out of scope when passing them to Rust.
The text was updated successfully, but these errors were encountered:
There are various places within our Swift library where we're not feeing memory used within Rust correctly or completely, which will cause memory leaks in an application which uses our library. Places we've found so far:
Util.collectTo
method copies memory when converting from Rust vectors to Swift arrays. We should free the underlying memory after copyingUtil.rustStringToSwift
) from Rust to Swift, we're calling free methods on the underlying Rust types, but we aren't doing anything when we move data from Swift into Rust (Util.rustStringToSwift
) which might also need work to freeThe text was updated successfully, but these errors were encountered: