Open Bug 1784165 Opened 2 years ago Updated 2 years ago

Allocate ArrayBuffer contents in the correct arena more of the time, and use the correct deallocator

Categories

(Core :: JavaScript Engine, defect, P3)

Product:
Core
Component:
JavaScript Engine
Type:
defect

Tracking

()

People

(Reporter: sfink, Unassigned)

References

(Blocks 1 open bug)

Details

ArrayBuffer contents that are malloced are supposed to be allocated in the js::ArrayBufferContentsArena, but especially when the contents are allocated separately that isn't always the case.

We should be able to use moz_arena_free(js::ArrayBufferContentsArena) to deallocate MALLOCED ArrayBuffer contents, which means making it always true (and switching cases where it isn't to use EXTERNAL with a specific deallocator or something).

Keywords: leave-open
Keywords: leave-open
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.