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

Redis + Kill may lead to segmentation fault #39

Closed
mpoquet opened this issue Jun 16, 2017 · 5 comments
Closed

Redis + Kill may lead to segmentation fault #39

mpoquet opened this issue Jun 16, 2017 · 5 comments

Comments

@mpoquet
Copy link
Collaborator

mpoquet commented Jun 16, 2017

The reason is unknown but it happened in https://gitlab.inria.fr/batsim/batsim/builds/9158.
The crash is deterministic.

@mpoquet
Copy link
Collaborator Author

mpoquet commented Jun 16, 2017

Might be related to the callback function after process exit.

MSG_process_on_exit(execute_profile_cleanup, cleanup_data);

@mpoquet
Copy link
Collaborator Author

mpoquet commented Jun 16, 2017

@adfaure: if you are looking for some funny debugging sessions, this bug can help you :D

@mickours
Copy link
Contributor

Is this still happening?

@mpoquet
Copy link
Collaborator Author

mpoquet commented Oct 22, 2018

Currently (548cd4b):

  • Kills are broken in some scenarios regardless of Redis (https://framagit.org/batsim/batsim/-/jobs/246085)
  • Memory deallocation on kill is not done. I'm waiting for a small s4u update to enable killing parallel tasks to completely get rid of MSG. =/

@mpoquet
Copy link
Collaborator Author

mpoquet commented Aug 20, 2021

Closing this issue as this should be fixed AND because redis is about to vanish.

@mpoquet mpoquet closed this as completed Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants