angular-ui/ui-grid

Memory Leak

Open

#4,802 opened on Dec 2, 2015

View on GitHub
 (8 comments) (3 reactions) (0 assignees)JavaScript (5,395 stars) (2,496 forks)batch import
help wantedneeds: answerseverity: memory leak

Description

Hi, I use ui-grid into my application. When i left a controller with a grid the memory is not released but i return into the same controller ( or other with another ui-grid) memory grows. I have same problem with yout tutorial.

I can released memory in any mode?

Contributor guide

Tech stack
angularjavascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
AngularJS basicsmemory profiling tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue describes a memory leak when leaving a controller with a ui grid, but lacks specific reproduction steps. Investigate the 'tutorial' mentioned and attempt to reproduce using the Angular UI Grid documentation examples. Check for common AngularJS memory leak sources such as event listeners on scopes not being cleaned up, DOM elements referenced in closures, or grid instances not being destroyed. Review the ui grid source code, especially controller lifecycle management and any destroy methods. Look at the 8 comments for any additional clues or attempted fixes.