Description of problem:
The latest F25 i686 update version of chromium-libs is several times larger than the release version (163M vs. 43M). The x86_64 version is not. Don't know if this should be considered a bug.
Version-Release number of selected component (if applicable):
Looking at koji builds, the issue exists in all F27 builds. In F26, chromium-libs-55.0.2883.87-1.fc26.i686.rpm is 46M, chromium-libs-56.0.2924.87-6.fc26.i686.rpm is 161M. I think there was a FTBFS before the F26 branch, and the size increased after that was fixed?
Bug (if that's what it is) still exists with latest Chromium 58 builds.
Okay, so here's why:
1) Chromium for i686 cannot build without turning down the debugging level. We OOM on the koji i686 builders. Thus, we pass -g1 to the compiler (only on i686).
2) Debuginfo generated for chromium is not useful. Because chromium is special.
Result: Overweight binary objects on i686.
I have not tried manually stripping them, because I suspect it will break chromium in weird and unpleasant ways. If you wish to experiment there, by all means, feel free, but I'm just as inclined to suggest you buy a more modern PC. :D
Please reopen if you have something we can do here.