[Testing Blixt v0.6] Creating/recovering wallet/channels - LND stop loading

[Darth-Coin]

This issue is not about live version! Is only about testing pre-release of v 0.6.0

Device: Android 8.1 Blixt: 0.6.0 rc1 (apk installed)

Steps I did for testing:

• installed fresh Blixt from apk
• create new wallet
• leave it to sync (blocks took 2-3 min, graph sync took another 12-14 min), In total is taking 530MB data space
• created a Dunder invoice for 200k sats and deposited from another Blixt wallet
• channel is open after few minutes (as it was expected) and ready to transact
• did a small test sending to a LN address, works nice

I wanted to make a channels backup:

• went to settings, click on export channels backup and nothing happen
• checked logs and says "prunning 11507 zombie channels"
• force closed the app
• disable cache graph sync before make a payment
• restart app
• go to settings, click on export backup channels, worked, letting me to select a folder on local device
• go back to settings and tried to verify backup. It doesn't do anything
• went to LND mobile help center, run the diagnostic and is stuck after first 2 points

Next intent

• force closed app and restart
• go to settings - channels backup - trying to select GDrive
• after few unresponsive clicks is opening a window from google asking which account to be used, selected but nothing happen after that.
• restarted app, go to settings, click again on Gdrive and now appeared a green message on the bottom saying the backup on google drive is activated. Indeed the selection stays.

Seems that are some issues delaying or not letting to happen those options for backup, is like unresponsive. Not sure if is not related with that sync graph thing. Seems that if is disabled that option, these functions works. Maybe is taking a lot of resources.

[Darth-Coin]

Seems that due to a bug in prunning zombie channels, the app just stale. After deleting the app and start a new wallet, the backup function and all other functions are working OK again. I will close this issue for now.

[Darth-Coin]

OK will re-open this one, because I have more updates, testing more with another device.

Environment

Samsung S3 with LineageOS Android 7.1.2 Blixt v 0.6.0 alpha2 apk (option "wait for graph sync disabled by default, not touched)

Steps to reproduce

• install Blixt directly from apk
• take seed + backup.channels from previous device / wallet
• start recovery process (insert seed + backup file)
• restore worked fine, appeared the message that is in course of sync
• after few min in Lightning Channels menu appeared the old channel in "waiting to close" state, but with no block hheight or txid
• checked lnd logs, it was still syncing gossip, trying to keep alive the app
• after a while appeared the notification popup that channel was closed, waiting for confirmation
• in onchain wallet transaction log also appeared a tx with the amount of recovered sats (link to txis on mempool goes to unconfirmed tx)
• waited a bit more and then appeared another 2 tx in onchain log with the same amount, but to another addresses (strange)
• went to logs to see what is going on, was still syncing and trying to broadcast that tx
• after few more minutes appeared the notification that tx was confirmed onchain and the tx appeared correctly in transactions log, also reflected in the onchain balance.
• all OK for a while and start personalizing Blixt: activated taproot, changed currency, activate Dunder, activate MPP
• closed app after a while, not just hide, closed the task
• restarted device
• open Blixt and immediately appeared at the bottom a red message saying "closed"
• went to lnd logs and it says:

  LTND: Shutting down because error in main method: unable to open databases: unable to obtain database backends: error opening bolt DB: cannot allocate memory
  2022-05-28 09:59:29.615 [INF] LTND: Shutdown complete

  Attached blixt lnd log blixt-lnd.log

Blixt app now it can't be used in this stage all functions are not responsive, only can enter in Settings and see those logs. Seems that lnd is loading all memory at start and then stop responding

More screenshots: