Closed
Bug 688456
Opened 14 years ago
Closed 13 years ago
Report memory usage of Firefox and plugin-container separately in Talos
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: justin.lebar+bug, Unassigned)
Details
Anode tells me that all our memory metrics on Talos report the sum of Firefox's and plugin-container's memory usage.
It seems to me that it would be more useful to report these two processes separately, since we control all of one process but little of the other.
Updated•14 years ago
|
Component: Release Engineering → Talos
Product: mozilla.org → Testing
QA Contact: release → talos
Version: other → Trunk
Comment 1•14 years ago
|
||
so would we want to report these as tp_rss_firefox, tp_rss_pluginprocess ?
tp_rss_flashprocess perhaps (if flash is the only plugin we use), but yes.
Should we go ahead and generalize this to include content processes as well? I think we're going to have to count content process memory sooner rather than later, so we might as well do it at the same time as this change.
| Reporter | ||
Comment 4•14 years ago
|
||
(In reply to Clint Talbert ( :ctalbert ) from comment #3)
> Should we go ahead and generalize this to include content processes as well?
> I think we're going to have to count content process memory sooner rather
> than later, so we might as well do it at the same time as this change.
sgtm!
Comment 5•14 years ago
|
||
I am handling this for osx in bug 693404. We already do this for android. Can we dup this bug, or should it be on for linux and windows?
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•