Repository navigation
Cross-thread URL.createObjectURL #46557
Description
What is the problem this feature will solve?
The blob url created with URL.createObjectURL is not accessible from the other threads when using buffer.resolveObjectURL.
The FileAPI defines that the blob url store is a per-agent setting: https://w3c.github.io/FileAPI/#url-model. A blob url created in the main thread should be accessible from the worker threads.
What is the feature you are proposing to solve the problem?
The blob url store should be shared across threads.
What alternatives have you considered?
This is explicitly documented as https://nodejs.org/api/url.html#urlcreateobjecturlblob:
Blob objects are registered within the current thread. If using Worker Threads, Blob objects registered within one Worker will not be available to other workers or the main thread.
We can keep this as is without the spec compliance.
Activity
jasnell commentedon Feb 8, 2023
Yep, it would be good to see this updated.
jimmywarting commentedon May 26, 2023
This would solve quite many things
import(blobUrl)fetch(blobUrl)new Worker(blobUrl)import()thingsBut there are some other blockers atm that dose not even accept blob urls in
Workerorimport()in the first place - even if the blob urls was constructed in the same thread as the blob where createdThere needs to be some central location (aka blob store) where it can keep track of which blobs do exist and how to access them from basically anywhere.
fursund commentedon Oct 21, 2023
Any way to work around this? What's the alternative way to do this instead of bloburl? Passing arraybuffers around?
github-actions commentedon Apr 19, 2024
There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-staleIssues and PRs exempt from automated stale handling.
label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
github-actions commentedon May 19, 2024
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
For more information on how the project manages feature requests, please consult the feature request management document.