-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fixed memory leaks in concurrent tests #1705
Fixed memory leaks in concurrent tests #1705
Conversation
43e2acd
to
089c72b
Compare
allocated: static Int = 0 | ||
freed: static Int = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This way we can actually remove the created classes, otherwise they could never be freed.
Peer review @erikhagglund ? |
Taking this off review again, I will add some more stuff. |
089c72b
to
82c3379
Compare
There we go. Peer review @erikhagglund or @sebastianbaginski , whoever has time |
@@ -84,6 +84,8 @@ ThreadTest: class extends Fixture { | |||
otherId free() | |||
(job as Closure) free() | |||
expect(myId equals(Thread currentThreadId()), is true) | |||
thisThreadInstance free() | |||
otherThreadInstance free() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not one line ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
82c3379
to
2f1c377
Compare
Part of the work on #1699
Eliminating these wasteful leaks have shown some leaks in
Promise
,PromiseCollector
, andThreadPool
that would occur if they're used in ways not currently used today. They will be fixed in a later PR.