Closed
Bug 934015
(long-term-leaks)
Opened 11 years ago
Closed 4 years ago
Finding long term memory leaks
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: akratel, Unassigned)
References
Details
(Whiteboard: [User Story], [mockup])
As a app/web developer I would like to find memory leaks over longer periods of time (>5 min) without having to run a recording so that I can find memory leaks without having to fill up my hard drive with excessive data that I don't need. Acceptance criteria: - Be able to take heap snapshots - be able to do diffs on the snapshots and find deltas on object counts Note: related to short term memory leak finds, different from that user story in that in this case, the goal is to find out if there are memory leaks over longer periods of time.
Updated•11 years ago
|
Whiteboard: [User Story], [mockup] → [User Story], [mockup][MemShrink]
Reporter | ||
Updated•11 years ago
|
Flags: pm-scrub?
![]() |
||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•11 years ago
|
||
This is not a duplicate, this is a user story that is there to track 625846 and others. Bug 625846 is just a bug that says we need a tool that Google has, that's not how we want to approach the problem if we want to come up with superior and better ways of doing this.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
![]() |
||
Comment 3•11 years ago
|
||
I dup'd it becaue comment 0 and bug 625846 comment 11 are almost identical. But if you want to have two bugs open for vague, almost-identical descriptions of heap analysis tools, I won't stop you.
Whiteboard: [User Story], [mockup][MemShrink] → [User Story], [mockup]
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•4 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•