Open Bug 1409953 Opened 7 years ago Updated 2 years ago

Make PCToLineNumber stop hanging the Gecko profiler

Categories

(Core :: JavaScript Engine, enhancement, P2)

53 Branch
enhancement

Tracking

()

Tracking Status
firefox58 --- wontfix
firefox59 --- ?

People

(Reporter: bzbarsky, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [js:tech-debt][js:testability])

The real underlying problem here is bug 929950, but that doesn't seem to have real traction. In the meantime, could we do something where the Gecko profiler gives up on accurate JS line/column information if it would take too long to gather it? For my typical use cases (profiling C++ code, mostly), the JS line/column info is not useful anyway.... (But yes, sometimes it's been helpful.) Right now I can't use the Gecko profiler as part of my normal browsing, because with near-certainty it will completely lock up my browser soon after startup with my normal set of tabs. :( Naveed, if we could get this fixed this would make it a lot easier to convince people to normally browse with the Gecko profiler turned on.
Flags: needinfo?(nihsanullah)
Assignee: nobody → jorendorff
Depends on: 929950
Flags: needinfo?(nihsanullah)
Priority: -- → P2
Whiteboard: [js:tech-debt][js:testability]

The bug assignee didn't login in Bugzilla in the last 7 months.
:sdetar, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: jorendorff → nobody
Flags: needinfo?(sdetar)

We should still fix this at some point.

Flags: needinfo?(sdetar)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.