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
Angular, SharePoint and IE11, Edge = Memory Leak #14555
Comments
did you enable prod mode? |
yes prod mode enabled and repro updated, we have a environment setup if you want to try it out i can hand out some login information |
Can you create a repository that we can clone that demonstrates this? |
@andtii Can you provide the code they are inserting into the content editor web part? |
@mike-morrison @DzmitryShylovich Here is the code in the script editor webpart <script type="text/javascript" src="https://mod114707.sharepoint.com/Pages/angular2.bundle.libs.js"></script> <script type="text/javascript" src="https://mod114707.sharepoint.com/Pages/helloworld.js"></script>And here is the code for helloworld component |
If someone wants to try it in SharePoint i can send you the login information. |
@mizzle-mo @DzmitryShylovich Intrested helping out here? We can give out Login information to anyone intrested in getting this solved |
@andtii did you try angular 4? |
@DzmitryShylovich Yes we tried angular 4 and still same problem |
@andtii We really need a simpler way of reproducing this... Could you try to bisect the problem? |
Closing to keep our bug tracker under control. Please reopen once you have a good way of reproducing the problem. Thanks! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Current behavior
Just by including Angular in a SharePoint environment a memory leaks starts to occur in IE11, Edge, for every page reload the memory increases and is never released until the browser is closed.
Expected behavior
No memory leak
Minimal reproduction of the problem with instructions
You can see that the memory is increasing and it is not released between page loads
What is the motivation / use case for changing the behavior?
Memory Leak = Bad, We have 60+ customers running IE getting memory leak until browser hangs
Please tell us about your environment:
We have a SharePoint Online environment ready where you can get the login information so that you can test the behavior!
Angular version: 2.3.0
Browser: IE11, Edge
The text was updated successfully, but these errors were encountered: