Yes, Android is excluded (for now). * Android + 32bit systems of any kind: PHC isn't even compiled-in, so the pref doesn't matter, but it is confusing to see the pref set to true (I can fix that). * 64bit desktop: PHC is compiled in, and now defers to the pref memory.phc.enabled. Which is set by the experiment. * If PHC is compiled in and the pref is true: PHC checks if there is at least 8GB of RAM (another pref) and only enables if this is true.
Another question/clarification I saw elsewhere was about whether this will always be an experiment. No. it's my intention that it'll eventually default-on in most cases. It may have memory limits or even adjust how much memory it uses depending on the physical ram available. On Sat, Jan 6, 2024 at 5:24 AM Daniel Veditz <[email protected]> wrote: > Not a definitive answer, but I've seen crash reports on Windows, Mac, > and Linux, but none on Android. The pref (memory.phc.enabled) is true > on Fenix nightly but I don't know if Android is included in the > roll-out experiment. PHC is not very aggressive to keep the > performance and memory impacts down, so we won't see many of these > instrumented crashes until it's rolled out to a very large audience. > > Another factor: PHC is only enabled on machines with 8Gb of memory > which might exclude a lot of android devices > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CANdLaqC7vxAxN4WtTXM%2ByGg1OMKQL%3D3cGJCmLZZ8FyNYeproKw%40mail.gmail.com.
