Some background on the original decision to ban static initializers:
http://neugierig.org/software/chromium/notes/2011/08/static-initializers.html
Note: Another name for static initializers is “global constructors”.
Common fixes include:
base::NoDestructor
.For Linux:
tools/linux/dump-static-initializers.py out/Release/chrome
For Android (from easiest to hardest):
# Build with: is_official_build=true is_chrome_branded=true # This will dump the list of SI's only when they don't match the expected # number in static_initializers.gni (this is what the bots use). ninja chrome/android:monochrome_static_initializers # or: tools/binary_size/diagnose_bloat.py HEAD # See README.md for flags. # or (the other two use this under the hood): tools/linux/dump-static-initializers.py --toolchain-prefix third_party/android_ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi- out/Release/lib.unstripped/libmonochrome.so # arm32 ^^ vv arm64 tools/linux/dump-static-initializers.py --toolchain-prefix third_party/android_ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android- out/Release/lib.unstripped/libmonochrome.so # Note: For arm64, having use_thin_lto=true seems to dump a couple extra # initializers that don't actually exist.
The last one may actually be the easiest if you've already properly built libmonochrome.so
with is_official_build=true
.
If the source of the new initiazers is not obvious from Step 1, you can ask the compiler to pinpoint the exact source line.
"//build/config/compiler:wglobal_constructors"
to default_compiler_configs
configs
in //base:base
treat_warnings_as_errors=false
diagnose_bloat.py
, refer to its README.md