I'm seeing a lot of temporary memory use (i.e. churn rather than a leak) in my memory analysis related to hash tables of InterfaceProviderSpecs.
From my understanding, all maps and sets declared in interface_provider_spec.h are good candidates for using base::flat_map and base::flat_set.
I started trying to convert them but ran into lots of serialization goop that was more work than I had time for.
If somebody looks into this, please check with me about serialization as we want to avoid creation of flat_maps one-element-at-a-time.
Comment 1 by brettw@chromium.org
, Apr 5 2017