wallet-core: [KMP] Memory leak found in AnyAddress
Describe the bug I found a memory leak in AnyAddress within the Kotlin package of Wallet Core.
dependencies {
implementation "com.trustwallet:wallet-core-kotlin-android:4.1.7"
}
To Reproduce The following code can trigger a memory leak:
println("Test started")
val publicKeyHex = "044ba28b11af1561042b03b9d0f940446315af11358aa12d798050b3cf76265dab0f48b22ea1fc1f9560c969b966221f2821b746c4e56efaeaeec8689caf5843c9"
var i = 1
while (i <= 1_000_000) {
val publicKey = PublicKey(publicKeyHex.hexToByteArray(), PublicKeyType.SECP256k1Extended)
val anyAddress = AnyAddress(publicKey, Ethereum, Derivation.Default) // This leaks memory!
if (i % 10_000 == 0) {
println("Test case $i run")
}
i++
}
println("Test completed")
Expected behavior No memory leak.
Screenshots
Memory Profiler Screenshot:
Additional context The above test was conducted on Android. Based on the generated code in directory wallet-core-kotlin, this issue should also exist on iOS.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 26 (17 by maintainers)
Hi @10gic, we don’t want to merge dev into master until we are sure memory leaks fixed. Unfortunately, our KMP engineers are busy right now to debug and improve GC experience. I’ll try to prioritise the work on this issue this week, thank you for the reminder
@10gic I scheduled a call this Friday with Kotlin engineers from another team. One of the ideas is to use native Swift, Java, JS wrappers to free the memory. Unfortunately, I can’t fully dedicate to the memory leaks as I’m currently focused on BTC PSBT, but will do the research and PR review end of this week
Hi @satoshiotomakan, the pr https://github.com/trustwallet/wallet-core/pull/4031 only try to fix the issue https://github.com/trustwallet/wallet-core/issues/4030.
Issue https://github.com/trustwallet/wallet-core/issues/4030 and issue https://github.com/trustwallet/wallet-core/issues/4021 are two different types of memory leaks.
Issue https://github.com/trustwallet/wallet-core/issues/4021 hasn’t been fixed yet.