angular-ui/ui-grid

headerCanvas, headerViewPort Memory Leak

Open

#3,889 opened on Jun 29, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (2,496 forks)batch import
help wantedseverity: memory leakseverity: performancetype: bug

Repository metrics

Stars
 (5,395 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I am running into a huge memory leak problem, where memory usage increase by 50m+ every time I switch between tabs in a single page application.

Grids are dynamically generated depending on the configuration of tab objects pulled asynchronously from a restful service. Each tab can contain up to four grids.

I followed the "three snapshot" technique and narrowed the problem down to thousands of RED nodes under headerCanvas and headerViewPort objects under containerCtrl.

memory_leak

ENV

AngularJS v1.3.16
UI-Grid 3.0.0-rc.21
Memory leak confirmed on IE11, Firefox, and Chrome

I have tried upgrading to RC 22 and upgraded Angular to 1.3.16. The problem still persist.

Contributor guide

Research direction
Profile memory snapshots in Chrome DevTools to identify retained nodes under headerCanvas and headerViewPort; check for event listeners or scope watchers not being cleaned up when tabs are switched.
Tech stack
javascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
AngularJSbrowser debugging tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60