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.

Sign up for GitHub

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

Jump to bottom

Probable memory corruption somewhere in task #102

Closed
msm-code opened this issue Apr 30, 2020 · 2 comments
Closed

Probable memory corruption somewhere in task #102

msm-code opened this issue Apr 30, 2020 · 2 comments
Assignees
@msm-code
Labels
level:medium This issue is of average difficulty priority:medium Priority: medium status:up for grabs This issue is a good candidate for PR type:bug Something isn't working

Comments

@msm-code
Copy link
Contributor

No other symptoms, but this screen (happened once):

ss

connection ID and task id doesn't look right (uninitialised memory maybe?)
@msm-code msm-code added level:medium This issue is of average difficulty priority:medium Priority: medium status:up for grabs This issue is a good candidate for PR type:bug Something isn't working labels Apr 30, 2020
@msm-code
Copy link
Contributor Author

When I think about it, TaskSpec memory is shared between snapshots, and we probably don't do a deep copy here. I'll try to reproduce it locally.

@msm-code msm-code self-assigned this Apr 30, 2020
@msm-code
Copy link
Contributor Author

(fixed with #104)

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

@msm-code msm-code

Labels
level:medium This issue is of average difficulty priority:medium Priority: medium status:up for grabs This issue is a good candidate for PR type:bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msm-code