Open Bug 657458 Opened 14 years ago Updated 3 years ago

Expose js::Foreground::free outside of js

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect

Tracking

()

People

(Reporter: justin.lebar+bug, Unassigned)

References

Details

We really want to call js::Foreground::free in bug 656911, but end up calling JS_free instead, because that's the best we've got.
Blocks: 656911
Should JS_free even be calling the background free thing anyway? It seems that JSAPI users probably aren't calling JS_free so many times that we need to do it on a background thread, and something simpler and more direct would be easier for them to use.
Blocks: 656991
No longer blocks: 656911
As John noticed, I typoed the bug number in comment 0. It should be 656991.
Do you still need this? It's been a week or two. But we should fix it if it helps you.
I don't appreciate the differences between JS_free and js::Foreground::free. I have code calling the former which apparently should be calling the latter. It's not many or particularly large allocations. Maybe you can tell me: Do I need this fix? (JSAutoStructuredCloneBuffer, used by indexdb has the same problem.)
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.