firefox-devtools / firefox-devtools/profiler
Removing profiler instrumentation stacks from native allocations and from js allocations
Open
memory
polish
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 491
- Avg merge
- 3d 46m
- Merged PRs (30d)
- 27
Description
It's confusing to users to see stacks like:
```
js::SavedStacks::MetadataBuilder::build(JSContext*, JS::Handle, js::AutoEnterOOMUnsafeRegion&) const
JS::Realm::setNewObjectMetadata(JSContext*, JS::Handle)
js::NativeObject::create(JSContext*, js::gc::AllocKind, js::gc::InitialHeap, JS::Handle, JS::Handle)
js::CallObject::create(JSContext*, JS::Handle, JS::Handle)
js::jit::NewCallObject(JSContext*, JS::Handle, JS::Handle)
0x2a049c82fb1e
bind_bindFunction1
bind
o
Contributor guide
Assessment
This issue has not been assessed yet.