Closed Bug 1341887 Opened 7 years ago Closed 7 years ago

Add fuzzing.enabled to gInitPrefs in FUZZING builds

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla54
Tracking Status
firefox54 --- fixed

People

(Reporter: mccr8, Assigned: mccr8)

References

Details

Attachments

(1 file)

This pref is used very early in start up, along with the other JS engine prefs, so I think it needs to be added to the white list, in fuzzing builds.
Blocks: 1341901
This will bitrot bug 1341414 so I can just wait until it lands. Clearly nobody is actually using fuzzing builds. ;)
Depends on: 1341414
Comment on attachment 8840174 [details]
Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds.

https://reviewboard.mozilla.org/r/114672/#review117236
Attachment #8840174 - Flags: review?(wmccloskey) → review+
I think the right solution here is to fix XPConnect's ReloadPrefsCallback to run a little later so that we don't hit this assertion. But since this one was already there, it's not fair to make you do that.
Pushed by amccreight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/737092ef7a83
Add fuzzing.enabled to gInitPrefs in FUZZING builds. r=billm
https://hg.mozilla.org/mozilla-central/rev/737092ef7a83
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.