https://apps.facebook.com/cookingmama_letscook/ doesn't work on Nightly 64-bit

RESOLVED WORKSFORME

Status

()

Core
JavaScript Engine
P3
normal
RESOLVED WORKSFORME
2 months ago
a month ago

People

(Reporter: alex_mayorga, Unassigned)

Tracking

({64bit, nightly-community})

57 Branch
x86_64
Windows 10
64bit, nightly-community
Points:
---

Firefox Tracking Flags

(firefox56 affected, firefox57 affected, firefox58 affected)

Details

(URL)

(Reporter)

Description

2 months ago
¡Hola!

Pre-requisites:
- Remove Adobe Flash from the system
- Logon into a facebbok.com account

Steps:
- Load https://apps.facebook.com/cookingmama_letscook/

Result:
This error message appears:

An error occured running the Unity content on this page. See your browser's JavaScript console for more info. The error was:
SecurityError: The operation is insecure.

This is logged to the console:

This page would be loaded into a new process due to a Large-Allocation header, however the creation of Large-Allocation processes is disabled on non-Win32 platforms.

Expected result:
The game is playable.

¡Gracias!
Alex

Updated

2 months ago
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
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?
Flags: needinfo?(luke)
Priority: -- → P3

Comment 2

2 months ago
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.
Flags: needinfo?(luke)
(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.
(Reporter)

Updated

2 months ago
status-firefox58: --- → affected
(Reporter)

Comment 4

a month ago
¡Hola Nika!

I wonder if this is something specific to this laptop then...

It fails just the same on Firefox Release 56:

An error occured running the Unity content on this page. See your browser's JavaScript console for more info. The error was:
SecurityError: The operation is insecure

Will try a fresh profile now.

¡Gracias!
Alex
status-firefox56: --- → affected
(Reporter)

Comment 5

a month ago
¡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
Status: NEW → RESOLVED
Last Resolved: a month ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.