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

Parity crashes on wifi reconnect. #5458

Closed
russdirks opened this Issue Apr 15, 2017 · 13 comments

Comments

Projects
None yet
4 participants
@russdirks

russdirks commented Apr 15, 2017

I've been running Parity on Windows 10 for about 3-4 months now, and it crashes every 5-10 days, more or less. Up until about 3 weeks ago I was running an old version of Parity (1.4 I think), but for the last 3 weeks I've been running 1.6.5. It has crashed 3 times since then. Here is the latest crash dump:

Faulting application name: parity.exe, version: 0.0.0.0, time stamp: 0x58da29f9
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f
Exception code: 0xc0000374
Fault offset: 0x00000000000f8283
Faulting process id: 0x2cc
Faulting application start time: 0x01d2b3d51af74e1c
Faulting application path: C:\Program Files\Ethereum\Parity\parity.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 95ab31e1-d6c3-4da7-9cc3-cec171e63a55
Faulting package full name: 
Faulting package-relative application ID:

I've used MemTest to test my memory and everything checks out ok. I tried monitoring RAM useage, and didn't see anything abnormal ... no increased memory useage that I could see.

My command line is as follows : --chain=classic --jsonrpc-interface all --jsonrpc-hosts all --jsonrpc-port 8545 --author 0x....

My .toml file is as follows:

chain = "classic"

[rpc]
port = 8545
interface = "all"
hosts = ["all"]

[mining]
author = "0x...."

[network]
bootnodes = ["enode://7ff0a073bf2ee9e94fae86de914eca0c0266c0b7051f4592ff0e9820706a085919ea667459897cde4efe3f0465f608cf402bde861983ce6ae3f9185df371aea7

Let me know if you want me to run any diagnostics and special logging.

@5chdn

This comment has been minimized.

Show comment
Hide comment
@5chdn

5chdn May 9, 2017

Member

This issue is labelled with panic: The client panics and exits without proper error handling. It's inactive for one month and neither assigned nor linked to a milestone.

@paritytech/core-devs Please, assign a developer to this issue and decided on a deadline within 7 days.

Member

5chdn commented May 9, 2017

This issue is labelled with panic: The client panics and exits without proper error handling. It's inactive for one month and neither assigned nor linked to a milestone.

@paritytech/core-devs Please, assign a developer to this issue and decided on a deadline within 7 days.

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks May 9, 2017

Just thought I would mention, since I reported this issue (24 days ago), it has not crashed once.

russdirks commented May 9, 2017

Just thought I would mention, since I reported this issue (24 days ago), it has not crashed once.

@arkpar

This comment has been minimized.

Show comment
Hide comment
@arkpar

arkpar May 10, 2017

Member

@russdirks Have you been running the same 1.6.5 version all this time?

Member

arkpar commented May 10, 2017

@russdirks Have you been running the same 1.6.5 version all this time?

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks May 10, 2017

I have been running 1.6.5 since about 3 weeks prior to reporting this issue all the way until now. In those 3 weeks prior it crashed 3 times.

russdirks commented May 10, 2017

I have been running 1.6.5 since about 3 weeks prior to reporting this issue all the way until now. In those 3 weeks prior it crashed 3 times.

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks May 11, 2017

I think I'll close this. If the problem starts reappearing I'll re-open or file a new issue.

russdirks commented May 11, 2017

I think I'll close this. If the problem starts reappearing I'll re-open or file a new issue.

@russdirks russdirks closed this May 11, 2017

@russdirks russdirks reopened this May 28, 2017

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks May 28, 2017

@arkpar, I figured out how to repo the issue ... just kill the wifi connection. I can make parity crash pretty reliably this way. Probably what was happening in the past was my wifi connection was dropping out occasionally. If you can't repo on a test machine let me know how to configure logging and I'll upload. Just a reminder, this is on Windows 10, ETC chain.

russdirks commented May 28, 2017

@arkpar, I figured out how to repo the issue ... just kill the wifi connection. I can make parity crash pretty reliably this way. Probably what was happening in the past was my wifi connection was dropping out occasionally. If you can't repo on a test machine let me know how to configure logging and I'll upload. Just a reminder, this is on Windows 10, ETC chain.

@5chdn

This comment has been minimized.

Show comment
Hide comment
@5chdn

5chdn May 29, 2017

Member

Could you run parity.exe from a command prompt and see what the exact panic message will be?

Member

5chdn commented May 29, 2017

Could you run parity.exe from a command prompt and see what the exact panic message will be?

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks May 29, 2017

There's no specific error message, just the standard Windows popup saying the program stopped working.

capture

I checked Windows Event viewer and found this:

Faulting application name: parity.exe, version: 0.0.0.0, time stamp: 0x58da29f9
Faulting module name: parity.exe, version: 0.0.0.0, time stamp: 0x58da29f9
Exception code: 0xc0000005
Fault offset: 0x0000000000b51cd0
Faulting process id: 0x374
Faulting application start time: 0x01d2d88d6a0f91ad
Faulting application path: C:\Program Files\Ethereum\Parity\parity.exe
Faulting module path: C:\Program Files\Ethereum\Parity\parity.exe
Report Id: 950ce372-2635-4c0c-a1a6-bea26e1f9e4a
Faulting package full name: 
Faulting package-relative application ID: 

russdirks commented May 29, 2017

There's no specific error message, just the standard Windows popup saying the program stopped working.

capture

I checked Windows Event viewer and found this:

Faulting application name: parity.exe, version: 0.0.0.0, time stamp: 0x58da29f9
Faulting module name: parity.exe, version: 0.0.0.0, time stamp: 0x58da29f9
Exception code: 0xc0000005
Fault offset: 0x0000000000b51cd0
Faulting process id: 0x374
Faulting application start time: 0x01d2d88d6a0f91ad
Faulting application path: C:\Program Files\Ethereum\Parity\parity.exe
Faulting module path: C:\Program Files\Ethereum\Parity\parity.exe
Report Id: 950ce372-2635-4c0c-a1a6-bea26e1f9e4a
Faulting package full name: 
Faulting package-relative application ID: 

@5chdn 5chdn changed the title from Parity crashes every 5-10 days to Parity crashes on wifi reconnect. Jun 9, 2017

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks Jun 23, 2017

Just wondering if there has been any progress on this? Any chance we will see something in the next release?

russdirks commented Jun 23, 2017

Just wondering if there has been any progress on this? Any chance we will see something in the next release?

@arkpar

This comment has been minimized.

Show comment
Hide comment
@arkpar

arkpar Jun 23, 2017

Member

We could not reproduce this exact issue, but a possible fix has been added to 1.6.8. Could you please check if it still crashes with the latest version?

Member

arkpar commented Jun 23, 2017

We could not reproduce this exact issue, but a possible fix has been added to 1.6.8. Could you please check if it still crashes with the latest version?

@russdirks

This comment has been minimized.

Show comment
Hide comment
@russdirks

russdirks Jun 23, 2017

Ok, I just upgraded to 1.6.8, did a complete re-synch, but I am still able to make Parity crash by cutting the wifi connection.

russdirks commented Jun 23, 2017

Ok, I just upgraded to 1.6.8, did a complete re-synch, but I am still able to make Parity crash by cutting the wifi connection.

@5chdn 5chdn added P2-asap 🌊 and removed P2-asap 🌊 labels Sep 4, 2017

@5chdn 5chdn added the hacktoberfest label Sep 27, 2017

@5chdn 5chdn modified the milestone: 1.8 Oct 5, 2017

@5chdn 5chdn modified the milestones: 1.8, 1.9 Oct 12, 2017

@5chdn 5chdn removed the hacktoberfest label Oct 31, 2017

@5chdn 5chdn referenced this issue Nov 16, 2017

Closed

Release next-beta 1.9.0 #7071

58 of 64 tasks complete

@5chdn 5chdn modified the milestones: 1.9, 1.10 Jan 23, 2018

@5chdn 5chdn referenced this issue Jan 26, 2018

Closed

Release next-beta 1.10 #7699

29 of 46 tasks complete
@brson

This comment has been minimized.

Show comment
Hide comment
@brson

brson Feb 2, 2018

Contributor

I can't reproduce this on master, commit 0ea1c41, whereas I can on 1.9.0, both built from source.

Contributor

brson commented Feb 2, 2018

I can't reproduce this on master, commit 0ea1c41, whereas I can on 1.9.0, both built from source.

@5chdn

This comment has been minimized.

Show comment
Hide comment
@5chdn

5chdn Feb 5, 2018

Member

Thanks for confirming!

Member

5chdn commented Feb 5, 2018

Thanks for confirming!

@5chdn 5chdn closed this Feb 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment