Bug 1815341 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I have a JSActor that is loading in very large binary blobs in the parent process, and then sending them to the content process. I want to make sure I'm doing this as efficiently as possible. For workers I can use transferables to ensure the memory is transferred and not copied. Is there any way to optimize the IPC call that is happening in the JSActor?

Example child request: https://searchfox.org/mozilla-central/rev/f078cd02746b29652c134b144f0629d47e378166/toolkit/components/translations/actors/TranslationsChild.sys.mjs#421-438

Example parent response: https://searchfox.org/mozilla-central/source/toolkit/components/translations/actors/TranslationsParent.sys.mjs#104-106
I have a JSActor that is loading in very large binary blobs in the parent process, and then sending them to the content process. I want to make sure I'm doing this as efficiently as possible. For workers I can use transferables to ensure the memory is transferred and not copied. Is there any way to optimize the IPC call that is happening in the JSActor?

Example child request: https://searchfox.org/mozilla-central/rev/f078cd02746b29652c134b144f0629d47e378166/toolkit/components/translations/actors/TranslationsChild.sys.mjs#421-438

Example parent response: hhttps://searchfox.org/mozilla-central/rev/f078cd02746b29652c134b144f0629d47e378166/toolkit/components/translations/actors/TranslationsParent.sys.mjs#104-106

Back to Bug 1815341 Comment 1