Bug 1742892 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
If the fission experiment is active the user cannot longer change the **Content process limit** because the options is missing, after turning off **Use recommended performance settings**. The only available option is **Use hardware acceleration when available**.

Removing these associated preferences from `prefs.js` restores the normal behaviour:

    user_pref("fission.experiment.max-origins.last-disqualified", 0);
    user_pref("fission.experiment.max-origins.last-qualified", 1637795116);
    user_pref("fission.experiment.max-origins.qualified", true);
    user_pref("fission.experiment.startupEnrollmentStatus", 4);

Tested with a clean profile. Steps to reproduce (Linux):

    $ mkdir /tmp/clean_profile
    $ firefox --profile /tmp/clean_profile

Quit, add the settings above to /tmp/clean_profile/prefs.js (otherwise automatically added by the experiment) and run again:

   $  firefox --profile /tmp/clean_profile

and after unticking **Use recommended performance settings** the **Content process limit** is missing. Removing the added preferences restores the normal UI.

This just happened to a normal user running Firefox 94 (main release) on a pretty old computer, while trying to modify the default content process limit so that Firefox properly runs there.
Revision 1 by
on 
If the fission experiment is active the user cannot longer change the **Content process limit** because the option is missing, after turning off **Use recommended performance settings**. The only available option is **Use hardware acceleration when available**.

Removing these associated preferences from `prefs.js` restores the normal behaviour:

    user_pref("fission.experiment.max-origins.last-disqualified", 0);
    user_pref("fission.experiment.max-origins.last-qualified", 1637795116);
    user_pref("fission.experiment.max-origins.qualified", true);
    user_pref("fission.experiment.startupEnrollmentStatus", 4);

Tested with a clean profile. Steps to reproduce (Linux):

    $ mkdir /tmp/clean_profile
    $ firefox --profile /tmp/clean_profile

Quit, add the settings above to /tmp/clean_profile/prefs.js (otherwise automatically added by the experiment) and run again:

   $  firefox --profile /tmp/clean_profile

and after unticking **Use recommended performance settings** the **Content process limit** is missing. Removing the added preferences restores the normal UI.

This just happened to a normal user running Firefox 94 (main release) on a pretty old computer, while trying to modify the default content process limit so that Firefox properly runs there.
Revision 2 by
on 
If the fission experiment is active the user cannot longer change the **Content process limit** because the option is missing, after turning off **Use recommended performance settings**. The only available option is **Use hardware acceleration when available**.

Removing these associated preferences from `prefs.js` restores the normal behaviour:

    user_pref("fission.experiment.max-origins.last-disqualified", 0);
    user_pref("fission.experiment.max-origins.last-qualified", 1637795116);
    user_pref("fission.experiment.max-origins.qualified", true);
    user_pref("fission.experiment.startupEnrollmentStatus", 4);

Tested with a clean profile. Steps to reproduce (Linux):

    $ mkdir /tmp/clean_profile
    $ firefox --profile /tmp/clean_profile

Quit, add the settings above to /tmp/clean_profile/prefs.js (otherwise automatically added by the experiment) and run again:

    $  firefox --profile /tmp/clean_profile

and after unticking **Use recommended performance settings** the **Content process limit** is missing. Removing the added preferences restores the normal UI.

This just happened to a normal user running Firefox 94 (main release) on a pretty old computer, while trying to modify the default content process limit so that Firefox properly runs there.
Revision 3 by
on 
If the fission experiment is active the user cannot longer change the **Content process limit** because the option is missing, after turning off **Use recommended performance settings**. The only available option is **Use hardware acceleration when available**.

Removing these associated preferences from `prefs.js` restores the normal behaviour:

    user_pref("fission.experiment.max-origins.last-disqualified", 0);
    user_pref("fission.experiment.max-origins.last-qualified", 1637795116);
    user_pref("fission.experiment.max-origins.qualified", true);
    user_pref("fission.experiment.startupEnrollmentStatus", 4);

Tested with a clean profile. Steps to reproduce (Linux):

    $ mkdir /tmp/clean_profile
    $ firefox --profile /tmp/clean_profile

Quit, add the settings above to /tmp/clean_profile/prefs.js (otherwise automatically added by the experiment) and run again:

    $ firefox --profile /tmp/clean_profile

and after unticking **Use recommended performance settings** the **Content process limit** is missing. Removing the added preferences restores the normal UI.

This just happened to a normal user running Firefox 94 (main release) on a pretty old computer, while trying to modify the default content process limit so that Firefox properly runs there.
Revision 4 by
on 
If the fission experiment is active the user cannot longer change the **Content process limit** because the option is missing, after turning off **Use recommended performance settings**. The only available option is **Use hardware acceleration when available**.

Removing these associated preferences from `prefs.js` restores the normal behaviour:

    user_pref("fission.experiment.max-origins.last-disqualified", 0);
    user_pref("fission.experiment.max-origins.last-qualified", 1637795116);
    user_pref("fission.experiment.max-origins.qualified", true);
    user_pref("fission.experiment.startupEnrollmentStatus", 4);

Tested with a clean profile. Steps to reproduce (Linux):

    $ mkdir /tmp/clean_profile
    $ firefox --profile /tmp/clean_profile

Quit, add the settings above to /tmp/clean_profile/prefs.js (otherwise automatically added by the experiment) and run again:

    $ firefox --profile /tmp/clean_profile

and after unticking **Use recommended performance settings** the **Content process limit** option is missing. Removing the added preferences restores the normal UI.

This just happened to a normal user running Firefox 94 (main release) on a pretty old computer, while trying to modify the default content process limit so that Firefox properly runs there.

Back to Bug 1742892 Comment 0