|
Title: How long does it take the Bisq Exchange app to load? Post by: JeromeTash on December 14, 2020, 04:31:19 PM Today I decided to check out Bisq through their app on Linux but the app has been stuck on this page for more than 15 minutes now
https://talkimg.com/images/2023/05/14/blob96efc82dca8271b6.png How long does one have to wait for the exchange to fully load? My internet network is good and my ISP doesn't block Tor Title: Re: How long does it take the Bisq Exchange app to load? Post by: LeGaulois on December 14, 2020, 04:44:22 PM A few seconds... and I have a 'not so good' network/ISP. Then another few seconds (or a few minutes if you have an average laptop with i.e. 6go ram) to synchronize the DAO. It eats a lot of memory if you haven't used it for a long time.
I tried just right now and it went fine. I remember once I had the same problem, I think because I was on an older version,( You may receive an error message, unrelated to the version if you still wait. Something about Runtime IIRC). I just closed the app and reopened it. I believe this is the reason you're unable to open it 'normally'=>the version. We're currently using 1.5.1 Title: Re: How long does it take the Bisq Exchange app to load? Post by: JeromeTash on December 19, 2020, 12:13:50 AM I believe this is the reason you're unable to open it 'normally'=>the version. Thanks the latest version works fine. The first time of setting it up took a good number of minutes but when I opened the application the second time, the exchange loaded in a fe secondsWe're currently using 1.5.1 Title: Re: How long does it take the Bisq Exchange app to load? Post by: o_e_l_e_o on December 19, 2020, 10:49:44 AM The most it has ever taken me is around 20 seconds, but I use it fairly frequency so I never have much data to sync. Very rarely it hangs on the startup screen for me even with latest version for reasons unknown - I suspect on these occasions it has connected to an out-of-date or otherwise faulty peer. I've never bothered to spend any time looking in to why since it is always solved by simply closing Bisq and relaunching.
|
