You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mentioned this thing before on Discord. Started Bolero on 8:48 and it crashed on 12:08. So worked more than 3 hours. I had this problem from the first official bolero version. It leaves an icon on the taskbar but when you try to click on it, the icon dissapears.
Hmm, the log does not have any suspicious things. The crash might be electron/frontend related. I am doing a complete revamp of the frontend system. This might fix the issue. Will investigate!
I had Bolero running on my home server (Win7, core i5, 16GB of RAM) for a week with no problems. Always synced with 7-12 neigbours. Today when logging in to the server I saw also that it crashed. After restart it reported it's back again at block 338k (even if it was synced as of yesterday). I left it there for an hour, but it was still at 338000, even with 8 nodes connected. I guess the database got corrupted. I will wait for the new version.
I mentioned this thing before on Discord. Started Bolero on 8:48 and it crashed on 12:08. So worked more than 3 hours. I had this problem from the first official bolero version. It leaves an icon on the taskbar but when you try to click on it, the icon dissapears.
There is the LOG:
current.log
The text was updated successfully, but these errors were encountered: