Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Memory Leak in 1.1.0 #1264

Closed
cesarblum opened this issue Dec 19, 2016 · 5 comments
Closed

Memory Leak in 1.1.0 #1264

cesarblum opened this issue Dec 19, 2016 · 5 comments
Assignees
@cesarblum
Labels
3 - Done bug patch-approved
Milestone
1.1.1

Comments

@cesarblum
Copy link
Contributor

cesarblum commented Dec 19, 2016 •
edited
Loading

Original issue: #1260

Should include this in 1.1.1.
@cesarblum
Copy link
Contributor Author

cc @muratg

@muratg
Copy link
Contributor

muratg commented Dec 19, 2016

Putting this in 1.1.1 for consideration.

@muratg muratg added this to the 1.1.1 milestone Dec 19, 2016
@Eilon
Copy link
Member

Eilon commented Jan 19, 2017

This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done.

@Eilon
Copy link
Member

Eilon commented Jan 19, 2017

@muratg please assign.

@halter73
Copy link
Member

We should make sure that #1311 also gets backported so the fix doesn't break timeouts on 32-bit platforms.

cesarblum pushed a commit that referenced this issue Jan 25, 2017
Fix memory leak caused by closure allocations in KestrelThread (#1264).
e2379b1
@cesarblum cesarblum mentioned this issue Jan 25, 2017
Merged
cesarblum pushed a commit that referenced this issue Jan 25, 2017
Fix memory leak caused by closure allocations in KestrelThread (#1264).
64c8887
cesarblum pushed a commit that referenced this issue Jan 29, 2017
Fix memory leak caused by closure allocations in KestrelThread (#1264).
e2a2e9a
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cesarblum cesarblum

Labels
3 - Done bug patch-approved
Projects
None yet
Milestone
1.1.1
Development

No branches or pull requests
4 participants
@halter73 @Eilon @cesarblum @muratg