Luke: Who knows about the large allocation impl? I would expect x64 to work with the header since, presumably, the address range exists to support the web application. Is this simply a case of too rigorous a guard?
Since the app is on x64, the Large-Allocation header shouldn't be necessary (there's plenty of address space), so I think that console message is a red herring. Michael, perhaps we should only display that on *32-bit* non-Windows? Probably the SecurityError is the real problem here and requires a separate investigation as to what operation is throwing it.
(In reply to Luke Wagner [:luke] from comment #2) > Since the app is on x64, the Large-Allocation header shouldn't be necessary > (there's plenty of address space), so I think that console message is a red > herring. Michael, perhaps we should only display that on *32-bit* > non-Windows? That console message was intended to make it clear to people who are testing the Large-Allocation header that we ignored it completely due to not being in a win32 build - it's definitely not related to the problem we're running into here which is the SecurityError. I'd feel weird about hiding it all together (because then you get no feedback for adding the Large-Allocation header outside of 32-bit windows), but I suppose that showing it in this case is a bit misleading (it caused confusion here), so perhaps we should. I tried loading this webpage on nightly on fedora, and it seems to work fine - no SecurityErrors are raised.
¡Hola everyone! Turns out this works with a fresh profile on both Release 56 and Nightly 58. Sorry about the wild goose chase =( Hope at least you've had some fun playing the game like my 4 years old does =) ¡Gracias! Alex