Closed Bug 1303517 Opened 3 years ago Closed 3 years ago
Are the Chrome
File Property Bag versions of the File constructor supposed to be usable in workers?
File::Constructor, say the overload taking a Blob and a ChromeFilePropertyBag, will check ThreadsafeIsCallerChrome() and then call InitializeChromeFile(). But InitializeChromeFile() does MOZ_ASSERT(nsContentUtils::IsCallerChrome()); which will assert mainthread... What is the intent here wrt workers?
> What is the intent here wrt workers? We should fix this. Currently that CTOR is used only for testing.
Assignee: nobody → amarchesini
smaug, bz doesn't accept reviews in these days...
Attachment #8792472 - Flags: review?(bugs)
Comment on attachment 8792472 [details] [diff] [review] blob_assert.patch r=me
Attachment #8792472 - Flags: review?(bugs) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/951db29640de File CTOR for chrome must be fully thread-safe, r=bz
Mark 51 as fix-optional. If it's worth uplift to 51, feel free to nominate it.
You need to log in before you can comment on or make changes to this bug.