And sure enough, bug 1828455 added https://searchfox.org/mozilla-central/rev/6602bdf9fff5020fbc8e248c963ddddf09a77b1b/js/src/vm/NativeObject.cpp#241 which would explain why it made it permanent. I suppose there are other cases where you can end up with capacity = 0 that would cause this intermittently in the past. So yes, it would seem like suppressions would be the only course of action, on the other hand, there doesn't seem to be one unique specific code path that could be used for a suppression.
Bug 1832153 Comment 84 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
And sure enough, bug 1828455 added https://searchfox.org/mozilla-central/rev/6602bdf9fff5020fbc8e248c963ddddf09a77b1b/js/src/vm/NativeObject.cpp#241 which would explain why it made it permanent. I suppose there are other cases where you can end up with capacity = 0 that would cause this intermittently in the past. So yes, it would seem like suppressions would be the only course of action, on the other hand, there doesn't seem to be one unique specific code path that could be used for a suppression that would pinpoint to slot allocations specifically.
And sure enough, bug 1828455 added https://searchfox.org/mozilla-central/rev/6602bdf9fff5020fbc8e248c963ddddf09a77b1b/js/src/vm/NativeObject.cpp#241 which would explain why it made it permanent. I suppose there are other cases where you can end up with capacity = 0 that would have caused this intermittently in the past. So yes, it would seem like suppressions would be the only course of action, on the other hand, there doesn't seem to be one unique specific code path that could be used for a suppression that would pinpoint to slot allocations specifically.