Closed Bug 1342399 Opened 9 years ago Closed 9 years ago

If you run "HeartbeatLongMessages" mock test in browser console, the browser becomes unresponsive

Categories

(Shield :: General, defect)

defect
Not set
blocker

Tracking

(firefox53 verified, firefox54 affected)

VERIFIED FIXED
Tracking Status
firefox53 --- verified
firefox54 --- affected

People

(Reporter: Ovidiu, Assigned: osmose)

References

()

Details

[Affected versions]: Firefox Nighlty 54.0a1(2017-02-23), Firefox Aurora 53.0a2(2017-02-23) [Affected platforms]: Mac OS X 10.10, Ubuntu 16.04, we didn't try on Win [Steps to reproduce]: 1. Set up my FF profile for testing 2. Run in Browser Console this: Cu.import('resource://shield-recipe-client/lib/Storage.jsm'); Storage.clearAllStorage(); Services.prefs.setCharPref("extensions.shield-recipe-client.api_url", "https://normandy-mock.dev.mozaws.net/HeartbeatLongMessages/api/v1"); Cu.import('resource://shield-recipe-client/lib/RecipeRunner.jsm'); RecipeRunner.start(); [Expected result]: The recipe is executed and you can interact with the browser. [Actual result]: After some time (~10 sec) the browser becomes unresponsive and all the screens flickers and CPU is more than 100%. Note: I also run the other 2 mock test recipe that contains Heartbeat and this issue doesn't reproduce.
Assignee: nobody → mkelly
Patch landed in mozilla-central in the sync from bug 1349348. This will be deployed to Beta 53 and Release 53 as a system add-on (bug 1351454).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified as fixed on Beta53 across Ubuntu 16.04, Win10, OSX 10.12
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.