Open Bug 1833827 Opened 2 years ago Updated 2 months ago

NativeObject::hasDynamicSlots is confusingly named

Categories

(Core :: JavaScript Engine, defect, P3)

Product:
Core
Component:
JavaScript Engine
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr102 --- unaffected
firefox113 --- unaffected
firefox114 --- unaffected
firefox115 --- wontfix

People

(Reporter: jonco, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

Since bug 1828455 landed hasDynamicSlots() can return true when numDynamicSlots() is zero, which is confusing. This is because it indicates whether there is an external dynamic slots allocation attached to the object, which is now also used to hold an object's optional unique ID.

Set release status flags based on info from the regressing bug 1828455

status-firefox113: --- → unaffected
status-firefox114: --- → unaffected
status-firefox115: --- → affected
status-firefox-esr102: --- → unaffected
Severity: -- → S3
Priority: -- → P3

:jonco nightly soft code freeze is next week, and the Fx115 merge day is on 2023-06-05.
Do you plan on fixing this for the 115 cycle or will it come in a later release?

Flags: needinfo?(jcoppeard)

This is not high priority so not currently planning to fix this cycle.

Severity: S3 → S4
Flags: needinfo?(jcoppeard)
Type: task → defect
Type: task → defect

I tried to make this a task but I guess that doesn't work because it is a regression? Ah well.

You need to log in before you can comment on or make changes to this bug.