I forgot for add one mroe screenshot. Later, when I analyze ccdump, I can
see circular references in my page. Please see the attached file.
Problem is - I do not know how to get rid of them and what is causing them
even on that simple web page.
Can you guys please help me with the memory leak problem?
thanks!
W dniu środa, 20 maja 2015 12:47:50 UTC+1 użytkownik gregs napisał:
>
> Hi,
> I am getting memory leaks in Firefox that are caused by populating serious
> numbers of orphan DOM elements in the browser. The env. details I am
> reproducing the error on:
>
> - firefox 31.x (but also tested on 37.x)
> - AngularJS 1.2.10 (but also tested on 1.3.15)
> - JBoss 7.1.x
>
> At the moment I have very small page, which initially was pretty rich but
> I ripped it of most of the stuff - just to keep an example as simple as it
> can be. The *main.html *looks like that now:
>
> <div id="searchPanel" class="panel panel-default">
> <div class="panel-body">
> <div class="row">
> <form name="searchForm" class="form-inline" ng-submit=
> "submitTestSearch()">
> <div>
> <div class="col-xs-7">
> <input id="searchButton" type="submit" class="btn
> btn-default" value="Get/Refresh"></input>
> </div>
> </div>
> </form>
> </div>
> </div>
> </div>
>
> As I said, this is extremely simple example. One form with only one
> button. This form is backed by a JS controller *MainCtrl*, which has the
> following method (the method is not doing anything special but that only
> for sake of simplicity):
>
> $scope.submitTestSearch = function() {
> console.log('fake submit');
> };
>
> The controller and the html page are bound together via $routeProvider
> object:
> $routeProvider
> .when('/subscriber',
> {
> templateUrl: 'js/profile-manager/main.html',
> controller: 'MainCtrl',
> resolve: {
> 'CustomizationConfig':
> 'SubscriberCustomizationConfigService',
> 'MainService': 'SubscriberService'
> }
> })
> .....
>
>
> Now, I have the problem with memory leaks and orphan objects in Firefox
> 31. The main.html is being rendered on 2 pages, accessible from 2 separate
> menu elements on the main page. The orphan objects are being left when the
> following scenario happens:
>
> 1. Go to 1st page
> 2. Click submit
> 3. Switch to 2nd page => orphan dom elements are left
> 4. Click submit
> 5. Switch back to 1st page => orphan dom elements are left
>
> As I look at *ccdump *output in my firefox, I can see a list of orphan
> objects left in the browser memory ( see the urls with profile-manager):
>
>
> <https://lh3.googleusercontent.com/-TeIQAP0y3ck/VVx0FLZ4qvI/AAAAAAAAMTk/x-MB-5H48k8/s1600/orphans1.JPG>
>
> <https://lh3.googleusercontent.com/-TeIQAP0y3ck/VVx0FLZ4qvI/AAAAAAAAMTk/x-MB-5H48k8/s1600/orphans1.JPG>
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
