Closed Bug 1751041 Opened 4 years ago Closed 4 years ago

Compute the process creation timestamp during startup

Categories

(Core :: mozglue, task)

Unspecified
All
task

Tracking

()

RESOLVED FIXED
98 Branch
Tracking Status
firefox98 --- fixed

People

(Reporter: gsvelto, Assigned: gsvelto)

References

Details

Attachments

(1 file)

We currently generate the process creation timestamp lazily, whenever someone requests it. This is causing me issues with the GC hazards detector in bug 1678152 because it thinks that we might be allocating memory while creating JS objects that require the process creation timestamp. I suppose we could just generate the timestamp greedily at startup to solve this particular problem. Every process we have requests it more than once so this wouldn't change anything in practice, we'd just move the computation sometimes earlier during process startup.

Previously the process startup timestamp was computed lazily but this caused
some issues with some of our static analysis infra (see bug 1678152). This
moves computing the timestamp early during process startup and makes it happen
unconditionally.

Depends on D132736

Assignee: nobody → gsvelto
Status: NEW → ASSIGNED
Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/034ae0e4c467 Compute the process startup timestamp early during startup r=glandium

I've inspected the issue and it's bug 1678152 causing it, so this can land on its own.

Flags: needinfo?(gsvelto)
Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bb7e7b27398f Compute the process startup timestamp early during startup r=glandium
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
Regressions: 1766342
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: