mutiny-web
mutiny-web copied to clipboard
MutinyWallet
Very high memory usage & lost balance in fedimint
Lost lot of sats and Mutiny just kept crashes in my phone during transaction due to out of memory, leading to numbers of sats being lost.
When opened in desktop, The balance only recovers at the small amount, but then also reveals that the memory usage is very big.
This is from 799 sats to this amount.
It just looks like it can't connect to the internet? Check your connections.
It just looks like it can't connect to the internet? Check your connections.
Connection is fine. Disconnection is mostly caused due to laggy machine when the browser starts taking my SWAP.
See whenever it's possible. Quite complicated to navigate or even getting the log at this point.
Anyway, I could not send sats via the web too. It immediately consume lot of RAM usages and the invoice became pending. Federation is "freedom one".
[Download Logs] Barely works at this point while the memory usage is slowly increasing to 1.9 GB again
Sorry. I could not get the log for now. The button just does nothing at this point.
@futurepaul what's the URL for the emergency page that doesn't load the node and other things?
I guess me losing my balance and the payment freezes because mutiny still tries to send sats with insufficient amount of sats for the fee. Still that should never happen but it ended up happening and ended up badly
refetching activity
index-DY19UVd9.js:123 ERROR mutiny-core/src/logging.rs:1372f33 2024-04-27 14:34:33.586 ERROR [mutiny_core::networking::socket:69] got an error reading event: Peer Sent Invalid Data
t.wbg.__wbg_error_8cf137381b3af25f @ index-DY19UVd9.js:123
6index-DY19UVd9.js:123 refetching activity
index-DY19UVd9.js:123 ERROR mutiny-core/src/logging.rs:1372f33 2024-04-27 14:35:18.069 ERROR [mutiny_core::networking::socket:69] got an error reading event: Peer Sent Invalid Data
t.wbg.__wbg_error_8cf137381b3af25f @ index-DY19UVd9.js:123
index-DY19UVd9.js:123 ERROR mutiny-core/src/logging.rs:1372f33 2024-04-27 14:35:34.597 ERROR [mutiny_core::networking::socket:69] got an error reading event: Peer Sent Invalid Data
t.wbg.__wbg_error_8cf137381b3af25f @ index-DY19UVd9.js:123
index-DY19UVd9.js:123 ERROR mutiny-core/src/logging.rs:1372f33 2024-04-27 14:35:34.606 ERROR [mutiny_core::networking::socket:69] got an error reading event: Peer Sent Invalid Data
t.wbg.__wbg_error_8cf137381b3af25f @ index-DY19UVd9.js:123
In console log
@futurepaul what's the URL for the emergency page that doesn't load the node and other things?
app.mutinywallet.com/settings/emergencykit
This issue is either caused by misbehaving fedimint federation or something messed up in mutiny-node.
So usually, When payment is failed, Mutiny then will restore the balance to your wallet. But if you keep doing it over and over again, which then randomly crashes at the pending stage, Mutiny will not restore your balance for some weird reasons.
That part is where weird things happen. As you try to zap without preserving atleast 1% of your balance (even with fedimint), Sometime fee checking just fails and gives 0 to mutiny. When that happens, You could basically try to send the entire balance of your wallet. But that will make another big disaster, which is what happend to me.
Once the second bug happens, The Fedimint federation that you joined will basically says "no" to every single [send] requests that you want to, and the balance will somewhat recover, except it wasn't and will consume A LOT of memory without reasons, which then leading to crash due to out of memory.
If you try to open again, Your balance will looks like it was cutted. Your previous sats invoice that pending or failed will never restored to your balance again. If only you try to send sats again, The memory usage will go spike up to 110% and then crashes your app or browser, again.
Trying to open again will make it refresh the balance. But still you will not be able to do anything with it as every single payment attempts that you try will simply gives pending result while the memory usage goes spiking up.
If that happens, congratulations. The only way out is to get out from the federation and use on-chain or other federation.
Try the new version released yesterday and upload logs again if that doesn't work. It's possible it's just due to a stuck payment and it'll resolve itself when it times out.
Try the new version released yesterday and upload logs again if that doesn't work. It's possible it's just due to a stuck payment and it'll resolve itself when it times out.
Noticed same slowdown at startup as previous version did. Setup Loading took more than 5 minutes to finish still. Will report further
Memory usage still goes high to 1 GB at some point (especially sending invoice) which is unusual. Will check on mutiny-logs tomorrow as i am away from laptop
On Android app, 0.6.8, app got killed due to OOM during Loading: Setup. Unable to get logs from it.
Note
Memory usage and startup duration dropped when defederated. Trying to join to the same federation again will lead to the same problem with the memory usage and startup duration
Memory usage is in 900 MB after startup
Then drops to 600 MB after this
Several seconds later, Goes up to 1 GB and freezes my laptop. Unable to get log as the Mutiny button freezes.
Pressing [Download Logs] instantly spikes the memory usage to 3.2 GB.
Update: Jumps to 4.5 GB for no reason
Chrome freezes. No result even after waiting for minutes for chrome to resolve.
Force stopping the chrome:
We'll take a look at the logs this week to see if we can find anything. Thank you for providing that.
Every now and then I see connection issues when it starts up. I also see some times where the nodes and everything shuts down. Are you manually stopping the node by chance?
It also seems like it occasionally works? I still see some times where invoices are created or attempted to be paid. I'm unsure if you're seeing issues every single time you start up, or if it's occasionally working, because the logs indicate that it occasionally works.
Could you describe your network setup? Are you using tor, what are you internet speeds, location, etc? All of this seems connectivity related. If it can't save to remote storage, or connect to the federations, all of this will cause issues.