Closed Bug 1048632 Opened 10 years ago Closed 9 years ago

[Meta] Memory leaks should be tracked and driven to goals for release

Categories

(Firefox OS Graveyard :: Performance, defect, P1)

Product:
Firefox OS Graveyard
Component:
Performance
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rdandu, Unassigned)

Details

(Keywords: memory-leak, perf, Whiteboard: [c=memory p=4 s= u=]) 

There is need to ensure that there are no memory leaks in common User interactions. This will ensure more stability for end user, and prevent reduced memory available to apps.  Propose to  track this metric for the FC/CC timeframes. 
1) Tests: Define a test case for checking the memory usage after a sequence of operations are done. 
2) Memory measurements: Memory usage (b2g-info) could be measured at the start and end of the test scenario. Example memory metrics tracked can be Used, B2G procs, Non-B2G and processes, Free, Cache, USS  PSS,RSS.  
3) Criteria: For CC timeframe for each release, memory leaks should be zero.
Keywords: perf
Whiteboard: [c=memory p= s= u=]
Assignee: nobody → wcosta
Keywords: mlk
Whiteboard: [c=memory p= s= u=] → [c=memory p=4 s= u=]
Priority: -- → P1
Status: NEW → ASSIGNED
Assignee: wcosta → nobody
Status: ASSIGNED → NEW
Close as wontfix. Please reopen if there is valid evidence of memory leak.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.