Successfully compiled asm.js code, storage initialization failed (consider filing a bug)

UNCONFIRMED
Unassigned

Status

()

Core
JavaScript Engine
P3
normal
UNCONFIRMED
a year ago
3 months ago

People

(Reporter: Peter, Unassigned, NeedInfo)

Tracking

({triage-deferred})

50 Branch
x86_64
Linux
triage-deferred
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8821827 [details]
Screenshot of output and message in Web Console

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161209095719

Steps to reproduce:

Download from https://github.com/tonyg/js-scrypt:
test_scrypt_browser.html
test_scrypt_browser.js
scrypt.js

Run example.


Actual results:

Web console reports:
---
12:30:40.298 Successfully compiled asm.js code (total compilation time 167ms; storage initialization failed (consider filing a bug)) 1 scrypt.js
12:30:40.409 pre-main prep time: 3 ms 1 scrypt.js:13:3478
---

Generated web page:
---
Firefox/50.0
Starting...
0123456789abcdef

Milliseconds for //16/1/1: 0
Milliseconds for password/NaCl/1024/8/16: 128
Milliseconds for pleaseletmein/SodiumChloride/16384/8/1: 149

...done.
---



Expected results:

Storage initialization should have worked.
(Reporter)

Comment 1

a year ago
Bug occurring with desktop Firefox 50.1.0.  Bug does not occur with mobile Firefox 50.0.2 on Android.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64

Comment 2

a year ago
WFM on Win10;
Fx50.0.2: Successfully compiled asm.js code (total compilation time 3076ms; stored in cache)
51.0b10: Successfully compiled asm.js code (total compilation time 423ms; caching disabled in FF51 due to bug; will be reenabled in FF52)
52.0a2 (2016-12-24): Successfully compiled asm.js code (total compilation time 344ms; stored in cache)
Component: Untriaged → Untriaged
Product: Firefox → Core

Updated

a year ago
Component: Untriaged → JavaScript Engine
The sounds like potentially an issue with a profile that was opened in a newer version of firefox and then downgraded back to an older version of FF.  Was this profile ever opened in 51+?  Does it reproduce in a fresh profile?
Flags: needinfo?(fedorowp)
(Reporter)

Comment 4

a year ago
The profile has never been opened with a newer version of Firefox.

At the moment, I am not in-front of the machine which generated the error, so I will retest with a fresh profile once I am.  However, I have tested using another machine with the same build of Firefox and same OS version, and the failure does -not- occur, which would fit the cause being profile corruption.

Retested with:
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161209095719
Keywords: triage-deferred
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.