1145894 - TreeModel in profiler does not correctly identify platform content loaded via file:/// when running local build

Status: RESOLVED INVALID

(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)

Description

[Jordan Santell [:jsantell] [@jsantell]]

Attachment: Screen Shot 2015-03-20 at 4.28.34 PM.png

Due to how we detect content, being no category, not having a chrome URL, and having a http:// or file:// protocol, when running locally, using a chrome JS (no category) in gecko, coming from file:// where my gecko-dev checkout lives, this passes the tests. See attachment

Comment 1

[Jordan Santell [:jsantell] [@jsantell]]

Check out http://todomvc.com/examples/react/#/, as there's a lot of nsAutoComplete stuff.

Comment 2

[Victor Porof [:vporof][:vp]]

I guess new pseudo stack entries were added without a category :/ We need to ask reviewers to r- such patches.

Comment 3

[Victor Porof [:vporof][:vp]]

Oh, now I see the screenshot in more detail and that's not a psentry. I saw nsAutoComplete and immediately assume a pseudo stack. Ignore comment 2.

Comment 4

[Jordan Santell [:jsantell] [@jsantell]]

Shu, is this a profiler issue for not being correctly tagged as platform code? Ran into this a few more times when working with source maps (as these look like local files), and appears to be certain files maybe loaded from file:// rather than resource/chrome.

Comment 5

[Jordan Santell [:jsantell] [@jsantell]]

This can be reproduced by recording on a new tab, as pretty much all content should be platform content, but we get a handful of frames from `file://{path-to-my-gecko-checkout}/obj.noindex/dist/Nightly.app/...` -- I wonder if we can just say if the URI is "dist/Nightly.app/Contents/Resources/components" (for each operating system), or if these scripts should be served over resource:// in the first place.

Comment 6

[Victor Porof [:vporof][:vp]]

Triaging. Filter on ADRENOCORTICOTROPIC (yes).

Comment 7

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug