Closed
Bug 1146533
Opened 10 years ago
Closed 10 years ago
JS profiler shows function calls from all open tabs
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 899853
People
(Reporter: antarticonorte, Unassigned)
References
Details
Attachments
(1 file)
491.41 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150322004013
Steps to reproduce:
Open one tab with some JS constantly running (like the spotify web player).
Open another tab you want to profile javascript in.
Actual results:
You can see function calls from the background tab in the profiler
Expected results:
Only function calls from the active tab should be shown
Reporter | ||
Updated•10 years ago
|
Component: Untriaged → Developer Tools: Performance Tools (Profiler/Timeline)
Comment 1•10 years ago
|
||
This is the nature of all content be in the same process, running single-threaded JS. Even if we could filter out this information, it would affect the current tab's performance, so hiding it would be inaccurate. Maybe we can summarize all "other tab" processing in a single frame node, showing the cost relative to the profile, so you can see if another tab is affecting performance on the current tab, without getting into the details.
Maybe the work in bug 674779 will allow us to single out which frames come from which windows, which would allow us to filter, and aggregate, "other tab" frames
Blocks: perf-tool-profilertree
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•10 years ago
|
||
Found a bug for this on the profiler's end, which where any filtering should be done anyway, and has more history there: bug 899853
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 3•10 years ago
|
||
Mistakenly filed against Firefox 38 and should be instead 38 Branch. Sorry for the spam. dkl
Version: Firefox 38 → 38 Branch
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•