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

[fixes #841] ensure testEnvironment.{beforeEach,afterEach} are released #842

Closed
wants to merge 1 commit into from

Conversation

stefanpenner
Copy link
Contributor

stefanpenner added a commit to ember-cli/ember-cli that referenced this pull request Aug 4, 2015
foundation set to mitigate some common memory leaks, still pending: qunitjs/qunit#842
@jzaefferer
Copy link
Member

Thank you for the contribution. Can you please sign our CLA? http://contribute.jquery.org/CLA/

@stefanpenner
Copy link
Contributor Author

Thank you for the contribution. Can you please sign our CLA? http://contribute.jquery.org/CLA/

Sent it to legal, lets see what they have to say.

@jzaefferer can you provide feedback now, I can atleast iterate to make sure this lands quickly. This leak is causing grief on many large apps, so we should try to get this in as soon as possible.

@@ -70,9 +70,11 @@ Test.prototype = {

config.current = this;

if (this.module.testEnvironment) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor style issue: Missing spaces inside if. Not sure why jscs didn't catch this.

@jzaefferer
Copy link
Member

The actual change looks good. I can fix the style issue when landing this, if you don't get around to it.

@stefanpenner
Copy link
Contributor Author

@jzaefferer style fixed, I'll push for +1 on the CLA quickly.

Are we looking at a quick turn-around on release once merged? (Just gotta plan how I can roll this out in the interim.)

@leobalter
Copy link
Member

I was looking at it, but then I had to stop for some scheduled meetings. It took me a while because I went to the original sources to take a deep look.

This fix seems good to me.

@leobalter
Copy link
Member

It also seems ok to release QUnit 1.19.0 after this.

leobalter pushed a commit to leobalter/qunit that referenced this pull request Aug 7, 2015
@leobalter
Copy link
Member

@stefanpenner

I'm ready to merge #842 I just need to confirm if you signed the CLA.

Merging it, I'll release QUnit 1.19, probably on Monday morning

@stefanpenner
Copy link
Contributor Author

Ya, still pending legal 👍.

@stefanpenner
Copy link
Contributor Author

sorry for the delay folks, still pending legal 👍

@leobalter
Copy link
Member

ok, I'm holding the 1.19 release until we get the approval.

@stefanpenner
Copy link
Contributor Author

Sorry about the delay, I have just gotten the legal 👍 and signed the CLA.

Apparently there was a small concern about some specific verbiage, if anyone is interested I can put them in contact with them. On a positive note, anyone at Yahoo! now has 👍 to contribute.

@leobalter leobalter closed this in fdf00a4 Aug 13, 2015
@leobalter
Copy link
Member

Thanks, @stefanpenner! It's merged now.

@stefanpenner stefanpenner deleted the fix-mem-leak branch August 13, 2015 15:55
@stefanpenner
Copy link
Contributor Author

sorry for the delay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants