Closed
Bug 1548510
Opened 5 years ago
Closed 5 years ago
Some profiler cleanups
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
- These functions do the same thing AFAICT so let's merge them:
- GeckoProfilerRuntime::strings is an ExclusiveData<> but it seems to be only accessed on the main thread. I want to put in an assert for this and then remove the locking.
Updated•5 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•5 years ago
|
||
This lock was necessary when the JITs used these strings (off-thread Ion compilation),
but now the lock was just adding overhead to each script we finalize etc.
This replaces ExclusiveData<> with MainThreadData<> to assert on-main-thread in debug
builds.
Assignee | ||
Comment 2•5 years ago
|
||
These functions did the same thing in a slightly different way.
Depends on D29798
Pushed by jdemooij@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/59086433eca1 part 1 - Remove unnecessary GeckoProfilerRuntime::strings lock. r=jonco https://hg.mozilla.org/integration/autoland/rev/39af0d6ccd3d part 2 - Deduplicate GeckoProfilerRuntime::allocProfileString and JitcodeGlobalEntry::createScriptString. r=jonco
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/59086433eca1
https://hg.mozilla.org/mozilla-central/rev/39af0d6ccd3d
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•