1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds

Status: RESOLVED FIXED

(Core :: DOM: Content Processes, defect)

Description

[Andrew McCreight [:mccr8]]

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.

Comment 1

[Andrew McCreight [:mccr8]]

This will bitrot bug 1341414 so I can just wait until it lands. Clearly nobody is actually using fuzzing builds. ;)

Comment 2

[Andrew McCreight [:mccr8]]

Attachment: Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds.

Review commit: https://reviewboard.mozilla.org/r/114672/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/114672/

Comment 3

[Andrew McCreight [:mccr8]]

Comment on attachment 8840174 [details]
Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds.

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/114672/diff/1-2/

Comment 4

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Comment on attachment 8840174 [details]
Bug 1341887 - Add fuzzing.enabled to gInitPrefs in FUZZING builds.

https://reviewboard.mozilla.org/r/114672/#review117236

Comment 5

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

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.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/737092ef7a83
Add fuzzing.enabled to gInitPrefs in FUZZING builds. r=billm

Comment 7

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/737092ef7a83