@SwissPrivateBanker I’ll get back as soon as I can. Instead of producing successes, I’m attempting all the ways in which the steps in this operation can go wrong.
@Mindphreaker Regarding first question, when did you clone the repos? I recently fixed that error you are receiving about the use of then. If you have the latest, I’ll take another look into what I missed.
For the second question, thank you to @bochaco for the explanation.
If I’m butchering this explanation, let it not reflect poorly on him.
In all cases, the allocated resources represented by a handle only have to do with local system heap and are not effecting network memory.
The good thing about the use of the SAFE browser is that even if calls are not made to free resources, those resources will be freed from system heap when the browser is closed and the JS garbage collector is triggered.
Same thing for use of safe_app_nodejs when making your own applications. Those resources will eventually be freed, when garbage collector is triggered.
I’m still learning our core Rust libraries, so I can’t speak very well to the low level but these libraries do have redundancies to ensure memory safety.
To your original question then, why do we then even need to manually free resources on the client?
When I’ve not freed resources, I’ve eventually run into generic errors and am no longer able to perform certain operations. So I think this is about managing the current client instance.
I’d like to replicate my errors and look more into this. Thank you for bringing it up.
@JesusTheHun Thank you for the question. You’re not stuck with the SAFE web API in the browser. You may use safe_app_nodejs API to allow applications, including electron applications, to interface with the network. See email app example