3430 - ie memory leak fixes - disable event caching, fixed resolver u…

[bbsteventill]

Reference Issue

…rl adding to root doc, and weak map ie issues

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[bbsteventill]

I signed it!

Bloomberg has added me to their cla

[email protected] " data-digest="From: [email protected] " style="">
From: [email protected]
Subject: Re: [Polymer/polymer] 3430 - ie memory leak fixes - disable event caching, fixed resolver u… (#3964)

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.
*If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.

*If you signed the CLA as a corporation, please let us know the company's name.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[googlebot]

CLAs look good, thanks!

[dtanp]

Our team found this problem and this patch helps to solve the problem (partially).

Another issue that causes the leak is HTML Import and we do a workaround by copying components.html to the main page.

Using both solutions together can significantly reduce the leak in IE, even though not totally fixed.

If this patch can be released at earliest, that would be great.

[bbsteventill]

FYI webcomponents/webcomponentsjs#644 fixes the memory leaks within web components

[dtanp]

thanks @bbsteventill !

[sorvell]

@azakus can you please review this? Thanks.

[jay8t6]

@azakus @sorvell when is the next release coming out? I'd love to see the performance improvement in IE.