JS marker EventHandlerNonNull has <unknown location> stack

NEW
Unassigned

Status

()

Firefox
Developer Tools: Performance Tools (Profiler/Timeline)
P3
normal
3 years ago
2 years ago

People

(Reporter: jsantell, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [devtools-platform])

Attachments

(1 attachment)

Created attachment 8602924 [details]
Screen Shot 2015-05-07 at 12.31.08 PM.png
Also see this on a EventListener.handleEvent
Apparently this is a localization that occurs when a frame contains neither a `source` or a `functionDisplayName`

Updated

3 years ago
Whiteboard: [devtools-platform]
Tromey, is this an intentional fallback when we can't determine a stack for some good reason, or an error?
Flags: needinfo?(ttromey)

Comment 4

3 years ago
I think it was defensive programming - so I would lean toward "error".

If we can't find a stack at all, then the stack properties on the marker should be null,
and we shouldn't try to display anything.

However, IIRC, at the time I wasn't sure if it was possible for a stack frame not to have
any useful descriptive information.
Flags: needinfo?(ttromey)

Comment 5

2 years ago
Do you know how I could reproduce this?
Flags: needinfo?(jsantell)
No idea, but I'll keep an eye out for it
Flags: needinfo?(jsantell)
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P3
Summary: [marker] JS Marker EventHandlerNonNull has <unknown location> stack → JS marker EventHandlerNonNull has <unknown location> stack
Version: 37 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.