Closed
Bug 1502686
Opened 6 years ago
Closed 6 years ago
Race condition when enabling Fuzzyfox
Categories
(Core :: DOM: Security, enhancement, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: tjr, Assigned: tjr)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 2 obsolete files)
When enabling fuzzyfox, if the JS Engine gets the current time before Fuzzyfox has run for the first time, we will return a completely old timestamp and are likely to cause a crash.
Updated•6 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Assignee | ||
Comment 1•6 years ago
|
||
Attachment #9022204 -
Flags: review?(amarchesini)
Comment 2•6 years ago
|
||
Comment on attachment 9022204 [details] [diff] [review] Bug 1502686 - When fuzzyfox is enabled, first put it into an initializing state before telling TimeStamp is it enabled r?baku Review of attachment 9022204 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/fuzzyfox/Fuzzyfox.cpp @@ +236,5 @@ > mStartTime = ActualTime(); > mDuration = PickDuration(); > > + LOG(Verbose, ("[FuzzyfoxEvent] PT(%p) For next time mDuration: %" PRIu32 " mStartTime: %" PRIu64 " \n", > + this, mDuration, mStartTime)); indentation here.
Attachment #9022204 -
Flags: review?(amarchesini) → review+
Assignee | ||
Comment 3•6 years ago
|
||
carry forward r+ from comment 2
Attachment #9022204 -
Attachment is obsolete: true
Attachment #9022214 -
Flags: review+
Assignee | ||
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by nerli@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/582dbb4c3bf5 When fuzzyfox is enabled, first put it into an initializing state before telling TimeStamp is it enabled r=baku
Keywords: checkin-needed
Comment 5•6 years ago
|
||
Backed out changeset 582dbb4c3bf5 (bug 1502686)for failing gtests on Contents/Resources/gmp-clearkey "CLOSED TREE" Backout revision https://hg.mozilla.org/integration/mozilla-inbound/rev/9d77e7bc0c9354e0a184c5e67278eb202c9bf3ac Backout push https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&resultStatus=testfailed%2Cbusted%2Cexception&classifiedState=unclassified&selectedJob=209505462&revision=9d77e7bc0c9354e0a184c5e67278eb202c9bf3ac Failed push https://hg.mozilla.org/integration/mozilla-inbound/rev/582dbb4c3bf56b635ad6238e75e886cba720ecf7 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=209504700&repo=mozilla-inbound :tjr Could you please take a look?
Flags: needinfo?(tom)
Assignee | ||
Comment 6•6 years ago
|
||
Carry forward r+ Patch adds a i != 0 condition to not crash gtest. Sorry!
Attachment #9022214 -
Attachment is obsolete: true
Flags: needinfo?(tom)
Attachment #9022275 -
Flags: review+
Assignee | ||
Comment 7•6 years ago
|
||
Okay, got a try run that seems pretty good, a few failures that seem to be existing intermittents.
Keywords: checkin-needed
Pushed by csabou@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/79fe86c6047b When fuzzyfox is enabled, first put it into an initializing state before telling TimeStamp is it enabled r=baku
Keywords: checkin-needed
Comment 9•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/79fe86c6047b
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in
before you can comment on or make changes to this bug.
Description
•