Skip to content
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

[Bug-Candidate]: echidna: thread blocked indefinitely in an MVar operation #1219

Open
rappie opened this issue Mar 18, 2024 · 9 comments
Open

Comments

@rappie
Copy link

rappie commented Mar 18, 2024

Describe the issue:

Getting the following error when closing Echidna:

echidna: thread blocked indefinitely in an MVar operation

Code example to reproduce the issue:

Private

Version:

Echidna 2.2.3 (custom latest build from master)

Relevant log output:

No response

@ggrieco-tob
Copy link
Member

Can you reproduce this consistently? We are very interested in getting this fixed since it is kind of a known issue but we don't have code to reproduce it.

@rappie
Copy link
Author

rappie commented Mar 18, 2024

Sadly i cannot reproduce it and the code is private 😞

@rappie
Copy link
Author

rappie commented Mar 20, 2024

Duplicate: #1209

@forkforkdog
Copy link

Running into this issue, can reproduce

@samalws-tob
Copy link
Collaborator

Anyone who's getting MVar errors: please run the catchMVarErrors branch on your codebase and tell me whether any "[MVar]: Error at ..." message appears before the normal "thread blocked indefinitely in an MVar operation" error message. This should help to pinpoint the cause of these problems

@ggrieco-tob
Copy link
Member

Anyone can confirm this is still an issue?

@blablalf
Copy link

blablalf commented Aug 5, 2024

Anyone can confirm this is still an issue?

I still have this issue on the v2.2.4

@ggrieco-tob
Copy link
Member

@blablalf can you try @samalws-tob 's suggestion using the catchMVarErrors branch?

@blablalf
Copy link

blablalf commented Aug 5, 2024

@blablalf can you try @samalws-tob 's suggestion using the catchMVarErrors branch?

Unfortunately, I can't reproduce the error at the moment, but if I do, I'll try catchMVarErrors and let you know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants