-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
16.0.0-RC2-beta keeps exiting automatically on Windows, at apparently random times #1168
Comments
@argakiig Is the Windows binary built in debug mode -- is it possible it is hitting an |
It's release, so shouldn't be hitting any assert, I was going to suggest building relwithdebinfo and getting a stack trace. I used to see this issue but it hasn't come up in a while. What block count are you on. Does it eventually pass on? |
Here's the log file from the next attempt, same result sadly:
|
Hmm, it doesn't seem to be getting past 226952 |
Ok... crashed again. |
I am attempting to replicate this on my end, If you are able to, could you build relwithdebinfo and get a stack trace from it? |
@argakiig, my IQ is definitely not high enough to do what you're requesting there. |
We'll keep working on this, if it's a major issue with V16 we'll release a patch release (V16.1) to fix it. As of right now it doesn't seem like this is a widespread issue, so I'm moving this to the next release to try to resolve. |
Also have been experiencing this issue on RC2. Didn't on RC1. Crashes consistently within 10 minutes of starting every time. Have tried deleting the database and resyncing - did not fix it. Logs show nothing suspicious. Windows 10 Pro x64 build 1803. |
I have the opposite problem in win10. It won't shut down properly! It keep existing process and restarting it several times will end up in multiple processes eating up all cpu. Not new for RC2 release though what I know. I think I saw it in RC1 and maybe also 15.2. |
with the latest release on the live network please verify whether this issue persists or not. |
It's not crashing anymore, and it's syncing so damn fast! |
Mainnet v16 seems to be fine over here too. |
While not crashing anymore, syncing after 2,4xx,xxx blocks downloaded is painfully slow, so slow that I gave up after a while. |
Also hasn't been smooth syncing here. Sorry this is now a bit off the original topic other than using win10. Noticed something seemed odd in the logs. From starting fresh at 12:01, by 16:56 showing: New sync is now crawling along very slowly. Have not published a receive for a pending incoming transaction. [edit: mainnet v16] |
Steps to reproduce the issue:
Additional information you deem important (e.g. issue happens only occasionally):
Nano > Bitcoin
Environment:
OS Name Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134
logs
There's nothing suspicious in the logs. Here's the last log as an example:
[2018-09-10 16:43:52.867855]: Node starting, version: 16.0
[2018-09-10 16:43:52.868852]: Work pool running 8 threads
[2018-09-10 16:43:52.868852]: Node ID: xrb_1x64x1qahseeia48sxcasap68daj1nwsxh7s4xp1tnd8ykh6tzrwiwtks46m
[2018-09-10 16:43:52.869850]: Starting bootstrap attempt
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Bootstrap stopped because there are no peers
[2018-09-10 16:43:52.869850]: Exiting bulk push client
[2018-09-10 16:43:52.869850]: Exiting bootstrap attempt
[2018-09-10 16:44:00.892872]: UPnP local address: , discovery: 0, IGD search: 3
[2018-09-10 16:44:00.892872]: UPnP device url: http://192.168.8.1:1990/WFADevice.xml st: upnp:rootdevice usn: uuid:873a6a1a-3dcd-4279-bd7f-5015b663ebc1::upnp:rootdevice
[2018-09-10 16:44:00.912818]: UPnP TCP mapping verification response: -1, external ip response: -1, external ip: , internal ip: 0.0.0.0, remaining lease:
[2018-09-10 16:44:00.923823]: UPnP UDP mapping verification response: -1, external ip response: -1, external ip: , internal ip: 0.0.0.0, remaining lease:
[2018-09-10 16:44:00.930763]: UPnP TCP port mapping response: -4, actual external port
[2018-09-10 16:44:00.937775]: UPnP UDP port mapping response: -4, actual external port
[2018-09-10 16:44:00.938742]: Starting bootstrap attempt
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Bootstrap stopped because there are no peers
[2018-09-10 16:44:00.938742]: Exiting bulk push client
[2018-09-10 16:44:00.938742]: Exiting bootstrap attempt
[2018-09-10 16:44:01.368766]: Found a representative at [::ffff:95.216.161.199]:54000
[2018-09-10 16:44:01.371859]: Found a representative at [::ffff:18.218.216.68]:54000
[2018-09-10 16:44:01.385718]: Found a representative at [::ffff:13.59.162.102]:54000
[2018-09-10 16:44:01.387677]: Found a representative at [::ffff:18.191.251.5]:54000
[2018-09-10 16:44:01.396899]: Found a representative at [::ffff:18.222.146.84]:54000
[2018-09-10 16:44:01.426824]: Found a representative at [::ffff:213.136.77.150]:54000
[2018-09-10 16:44:01.433131]: Found a representative at [::ffff:88.99.80.243]:54000
[2018-09-10 16:44:01.459916]: Found a representative at [::ffff:185.45.113.124]:54000
[2018-09-10 16:44:01.618956]: Found a representative at [::ffff:178.128.149.150]:54000
[2018-09-10 16:44:01.725680]: Found a representative at [::ffff:45.27.17.106]:54000
[2018-09-10 16:44:01.792558]: Found a representative at [::ffff:162.157.199.67]:54000
[2018-09-10 16:44:05.940071]: Starting bootstrap attempt
[2018-09-10 16:44:06.221035]: Received 1 frontiers from [::ffff:18.218.216.68]:54000
[2018-09-10 16:44:06.638577]: Completed frontier request, 63 out of sync accounts according to [::ffff:18.218.216.68]:54000
[2018-09-10 16:44:06.979273]: 65 blocks in processing queue
[2018-09-10 16:44:21.105985]: Found a representative at [::ffff:18.191.251.5]:54000
[2018-09-10 16:44:22.978061]: 45 accounts in pull queue
[2018-09-10 16:44:24.102961]: 65 blocks in processing queue
[2018-09-10 16:44:37.093746]: Found a representative at [::ffff:18.218.216.68]:54000
[2018-09-10 16:44:37.100729]: Found a representative at [::ffff:18.191.251.5]:54000
[2018-09-10 16:44:37.205714]: Found a representative at [::ffff:18.222.146.84]:54000
[2018-09-10 16:44:37.996910]: 27 accounts in pull queue
[2018-09-10 16:44:39.451602]: 66 blocks in processing queue
[2018-09-10 16:44:40.776638]: Block 41D0E5D2CD5F68EE09955401EC375C86B370F2861964D4ECC383B20F196D70B2 was republished to peers
[2018-09-10 16:44:54.488925]: 65 blocks in processing queue
[2018-09-10 16:44:54.982990]: 11 accounts in pull queue
[2018-09-10 16:44:57.141723]: Found a representative at [::ffff:18.222.146.84]:54000
[2018-09-10 16:45:05.109198]: Found a representative at [::ffff:18.191.251.5]:54000
[2018-09-10 16:45:12.828788]: 447 blocks in processing queue
[2018-09-10 16:45:28.777978]: Block 79DA6B983F8DCD074E5B39B464EAE17966773146DEAC6C23976A6772F083D85F was republished to peers
The text was updated successfully, but these errors were encountered: