Closed Bug 1342064 Opened 8 years ago Closed 8 years ago

Empty histogram not allowed

Categories

(Shield :: General, defect)

defect
Not set
blocker

Tracking

(firefox53 unaffected, firefox54 affected)

RESOLVED DUPLICATE of bug 1341996
Tracking Status
firefox53 --- unaffected
firefox54 --- affected

People

(Reporter: aflorinescu, Unassigned)

References

(Blocks 1 open bug)

Details

[Versions:] -tested on MacOSX10.10 and Ubuntu 16.04 -Reproducible on Nightly54 20170223110219 -Not Reproducible on Aurora53 20170223084136 [Description:] Running any recipe from normandy-admin or mock server will return unknown errors in browser console. (see http://imgur.com/a/v8gLj). [Steps:] 1. Connect to VPN. 2. Obtain a copy of Firefox with the SHIELD recipe client system add-on installed. (at the current time, nightly and aurora have the system add-on) 3. Set the extensions.shield-recipe-client.dev_mode preference to true to run recipes immediately on startup. 4. Set the extensions.shield-recipe-client.logging.level preference to 0 to enable more logging. 5. Set the security.content.signature.root_hash preference to DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90. 6. Restart Browser. (assuming there is at least 1 recipe to be executed) and open Browser console. ( or use a mock recipe from https://normandy-mock.dev.mozaws.net/) [Actual Result:] The normal shield console execution messages are displayed after which it starts pouring with unknown error messages as shown here: http://imgur.com/a/v8gLj (-after 10-15 minutes it doesn't seem to stop ) [Expected Result:] No console errors. [Note]: We also have some performance related issues that we think it might be related to this bug, since we haven't noticed them in prior tests, so for this reason, I'm going temporarily set the severity to blocker.
This could be bug 1341996
Depends on: 1341996
Thank you Mark. Further testing on this, I can actually confirm now that this is not related to Shield System Addon. Therefore marking it as a dupe after bug 1341996.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.