Open Bug 1555974 Opened 5 years ago Updated 2 years ago

Stop abusing NS_FREE_PERMANENT_DATA for profile/coverage atexit hook requirements

Categories

(Firefox Build System :: General, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: Gijs, Unassigned)

References

Details

(Keywords: in-triage)

We currently set NS_FREE_PERMANENT_DATA to true for pgo profiling (after bug 1196094) and code coverage (after bug 1460929). This is all to ensure we get atexit hooks. Ideally, we should use something more targeted to that problem.

Bugbug thinks this bug is a task, but please change it back in case of error.

Type: defect → task

Based on Comment Bug 1570619#c18, can we reprioritize this? We discussed this bug during platform triage today. Thanks.

+1 to Marcia's comment. This bug is flagged as something that would help a performance regression.

Flags: needinfo?(cmanchester)

Mike is working on this.

Assignee: nobody → mshal
Flags: needinfo?(cmanchester)
Priority: P3 → P2

I was working on this as a possible way to fix the perf regression in bug 1570619, but fixing this bug did not help the performance there. Do we want this changed even if there's no performance win?

Assignee: mshal → nobody
Priority: P2 → P3

(In reply to Michael Shal [:mshal] from comment #5)

I was working on this as a possible way to fix the perf regression in bug 1570619, but fixing this bug did not help the performance there. Do we want this changed even if there's no performance win?

I think so, yes, though I defer to :froydnj.

Flags: needinfo?(nfroyd)

(In reply to :Gijs (he/him) from comment #6)

(In reply to Michael Shal [:mshal] from comment #5)

I was working on this as a possible way to fix the perf regression in bug 1570619, but fixing this bug did not help the performance there. Do we want this changed even if there's no performance win?

I think so, yes, though I defer to :froydnj.

I agree that we would like this changed, for separation of concerns if nothing else.

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