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

canorus crashes on exit #120

Closed
matevz opened this issue Jan 1, 2020 · 5 comments · Fixed by #161
Closed

canorus crashes on exit #120

matevz opened this issue Jan 1, 2020 · 5 comments · Fixed by #161
Labels
bug Something isn't working

Comments

@matevz
Copy link
Member

matevz commented Jan 1, 2020

When python support is compiled in, Canorus crashes on exit with random errors like:

  • double free or corruption (out)
  • double free or corruption (!prev)
  • free(): invalid pointer

This is always reproducible on any operating system.

@matevz matevz added the bug Something isn't working label Jan 1, 2020
@suamor
Copy link
Collaborator

suamor commented Jan 3, 2020

In my experience this only happens with python plugins enabled.
Can you provide a stack trace for online discussion / analysis ?

@suamor
Copy link
Collaborator

suamor commented Jan 4, 2020

My branch shows the message "corrupted size vs. prev_size" before crashing.
Stackoverflow discussion on this:
https://stackoverflow.com/questions/49628615/understanding-corrupted-size-vs-prev-size-glibc-error
This was just a quick test if anything obviously not working with my changes applied.

@matevz
Copy link
Member Author

matevz commented Jan 4, 2020

Those errors are very tricky. For me it shows a different segfault location each time it crashes. IMO it's a python-releated crash on the same object being freed twice, possibly a race condition (maybe some missing mutex lock somwhere in destructors?)..

@matevz matevz added this to the add before next release milestone Jan 4, 2020
@matevz
Copy link
Member Author

matevz commented Jan 21, 2020

This might be solved once we use smart pointers accross the code (#133).

@suamor
Copy link
Collaborator

suamor commented Feb 29, 2020

PR #158 may fix this issue, please check and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants