Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Killing via Ctrl+C hangs on latest master #8540

Closed
tomusdrw opened this issue May 3, 2018 · 4 comments
Closed

Killing via Ctrl+C hangs on latest master #8540

tomusdrw opened this issue May 3, 2018 · 4 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@tomusdrw
Copy link
Collaborator

tomusdrw commented May 3, 2018

Happens randomly.

From @Tbaut

just happened on a synced node (wasn't synced before) with Parity/v1.12.0-unstable-b100945-20180502

@tomusdrw tomusdrw added F2-bug 🐞 The client fails to follow expected behavior. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels May 3, 2018
@trappist
Copy link
Contributor

Happens reliably here. It prints Finishing work, please wait... and never exits, I have to kill -9.

@dvdplm
Copy link
Collaborator

dvdplm commented May 22, 2018

Happens sporadically here (~1/day) using a variety of flags.

@niklasad1 niklasad1 assigned niklasad1 and unassigned niklasad1 Jun 4, 2018
@niklasad1
Copy link
Collaborator

@tomusdrw can we close this now when #8751 is merged?

@tomusdrw
Copy link
Collaborator Author

tomusdrw commented Jun 5, 2018

Yeah, let's re-open if the issue persists.

@tomusdrw tomusdrw closed this as completed Jun 5, 2018
@5chdn 5chdn added this to the 1.12 milestone Jun 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

5 participants