{"action":"created","issue":{"url":"https://api.github.com/repos/angular/angular/issues/17637","repository_url":"https://api.github.com/repos/angular/angular","labels_url":"https://api.github.com/repos/angular/angular/issues/17637/labels{/name}","comments_url":"https://api.github.com/repos/angular/angular/issues/17637/comments","events_url":"https://api.github.com/repos/angular/angular/issues/17637/events","html_url":"https://github.com/angular/angular/issues/17637","id":237275858,"number":17637,"title":"IE 11 Memory Leaking on Browser Reload","user":{"login":"derrickh1980","id":22606826,"avatar_url":"https://avatars2.githubusercontent.com/u/22606826?v=4","gravatar_id":"","url":"https://api.github.com/users/derrickh1980","html_url":"https://github.com/derrickh1980","followers_url":"https://api.github.com/users/derrickh1980/followers","following_url":"https://api.github.com/users/derrickh1980/following{/other_user}","gists_url":"https://api.github.com/users/derrickh1980/gists{/gist_id}","starred_url":"https://api.github.com/users/derrickh1980/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/derrickh1980/subscriptions","organizations_url":"https://api.github.com/users/derrickh1980/orgs","repos_url":"https://api.github.com/users/derrickh1980/repos","events_url":"https://api.github.com/users/derrickh1980/events{/privacy}","received_events_url":"https://api.github.com/users/derrickh1980/received_events","type":"User","site_admin":false},"labels":[{"id":375501288,"url":"https://api.github.com/repos/angular/angular/labels/comp:%20core%20&%20compiler","name":"comp: core & compiler","color":"c7def8","default":false},{"id":130606843,"url":"https://api.github.com/repos/angular/angular/labels/type:%20bug","name":"type: bug","color":"EEEEEE","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-06-20T16:45:31Z","updated_at":"2017-09-13T20:42:00Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nPLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.\r\n\r\nISSUES MISSING IMPORTANT INFORMATION MIGHT BE CLOSED WITHOUT INVESTIGATION.\r\n-->\r\n\r\n## I'm submitting a ...\r\n<!-- Check one of the following options with \"x\" -->\r\n<pre><code>\r\n[ ] Regression (behavior that used to work and stopped working in a new release)\r\n[x] Bug report <!-- Please search github for a similar issue or PR before submitting -->\r\n[ ] Feature request\r\n[ ] Documentation issue or request\r\n[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question\r\n</code></pre>\r\n\r\n## Current behavior\r\nWhen reloading an angular application, via the browser reload, in IE 11 the browser's memory continually builds until it crashes. \r\n\r\n## Expected behavior\r\nOn reload of the angular application in IE 11 the browser's memory will not build.\r\n\r\n## Minimal reproduction of the problem with instructions\r\n1. Run the demo plunker in IE11.\r\n    http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5\r\n2. Hit F12 and go to the memory tab and start the memory analyzer. Additionally you can open Task Manger in Windows and watch the Memory Usage.\r\n3. Click the green reload button to manually trigger a refresh of the preview.\r\n4. Continue to refresh and watch the memory increase on every refresh.\r\n\r\n## What is the motivation / use case for changing the behavior?\r\nI am building an enterprise level application. During testing, IE11 has crashed a few times due to this memory build up. The application I'm building is quite large and when I do the same steps as listed above I am getting jumps of 100+ MB per reload. The application should not build memory on reload so the browser won't crash.\r\n\r\n\r\n## Please tell us about your environment\r\n<pre><code>\r\nAngular version: 4.0.2\r\n\r\nBrowser:\r\n- [ ] Chrome (desktop) version XX\r\n- [ ] Chrome (Android) version XX\r\n- [ ] Chrome (iOS) version XX\r\n- [ ] Firefox version XX\r\n- [ ] Safari (desktop) version XX\r\n- [ ] Safari (iOS) version XX\r\n- [x] IE version 11.0.9600.17691 \r\n- [ ] Edge version XX\r\n \r\nFor Tooling issues:\r\n- Node version: 6.9.5 \r\n- Platform: Windows 7\r\n\r\nOthers:\r\n<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->\r\nI have done extensive testing to track down the memory leak with no success. I have tested \r\nthis against IE, Chrome, and FireFox. Chrome and Firefox do not show any signs of memory \r\nleakage. Here is a list of steps taken and environment setup. \r\n\r\nI use Visual Studio 2015.\r\nThe following three tests were done with the Visual Studio 2015 quick start guide.\r\nhttps://angular.io/guide/visual-studio-2015\r\n\r\nSetup 1:\r\nhttps://github.com/derrickh1980/IEAngularMemoryTester\r\nUsed an MVC template when starting the project.\r\nSet up to run on IIS.\r\nMemory jumps between 30 - 50 MB per reload.\r\n\r\nSetup 2:\r\nhttps://github.com/derrickh1980/IEAngularMemoryTester2\r\nUsed an empty website template when starting the project.\r\nSetup to run on IIS.\r\nMemory jumps between 30 - 50 MB per reload.\r\n\r\nSetup 3:\r\nhttps://github.com/derrickh1980/IEAngularMemoryTester3\r\nUsed an empty website template when starting the project.\r\nSetup to use lite-server\r\nMemory jumps between 30 - 50 MB per reload.\r\n\r\nI turned on prod mode on all three test environments with no change in results.\r\n\r\nBefore going to an empty angular application to test this I did a few things with my current \r\napplication.\r\nHere is my current application setup.\r\nBuilt on top of an MVC framework. (MVC is not required anywhere so this will probably change \r\nvery soon)\r\nIt is setup to run on IIS.\r\n\r\nFirst, I implemented ChangeDetectionStrategy.OnPush in my application. That did not affect \r\nthe memory leak.\r\n\r\nSecond, I tried unsubscribing to any subscribers I have setup on observables. That didn't \r\naffect the memory leak. I couldn't really be sure the ngOnDestroy() method was being hit \r\non reload so there was no way for me to tell if this change was actually doing anything \r\nanyway.\r\n\r\nThird, I upgraded my angular version to 4.2.3 which had no affect on the memory leak.\r\n\r\nFinally, I decided to go down to the lowest level and start with a brand new sample \r\napplication to see if I could replicate a memory leak which I was successful at doing. I \r\nknow that I may be introducing some memory leakage due to some coding practices \r\nbut I have to start with Angular because a simple sample application is causing \r\nmemory leakage.\r\n\r\nThanks in advance for any assistance with this.\r\n\r\n</code></pre>\r\n"},"comment":{"url":"https://api.github.com/repos/angular/angular/issues/comments/329290696","html_url":"https://github.com/angular/angular/issues/17637#issuecomment-329290696","issue_url":"https://api.github.com/repos/angular/angular/issues/17637","id":329290696,"user":{"login":"ladyleet","id":8270563,"avatar_url":"https://avatars0.githubusercontent.com/u/8270563?v=4","gravatar_id":"","url":"https://api.github.com/users/ladyleet","html_url":"https://github.com/ladyleet","followers_url":"https://api.github.com/users/ladyleet/followers","following_url":"https://api.github.com/users/ladyleet/following{/other_user}","gists_url":"https://api.github.com/users/ladyleet/gists{/gist_id}","starred_url":"https://api.github.com/users/ladyleet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ladyleet/subscriptions","organizations_url":"https://api.github.com/users/ladyleet/orgs","repos_url":"https://api.github.com/users/ladyleet/repos","events_url":"https://api.github.com/users/ladyleet/events{/privacy}","received_events_url":"https://api.github.com/users/ladyleet/received_events","type":"User","site_admin":false},"created_at":"2017-09-13T20:42:00Z","updated_at":"2017-09-13T20:42:00Z","author_association":"NONE","body":"@SusanHanson @RobertTeisanu ^^"}}
{"actor":{"display_login":"ladyleet"}}