There were exceptions in the early days when the team was still figuring things out. For example, release-branches were cut more sporadically, and the middle number was used to sorta-kinda represent smaller feature changes.
You might be thinking of release dates tied to a set of completed product features. Chrome doesn't work that way. The team ships on a regular schedule, holding back features that aren't ready for the public. Frequent releases help mitigate the urge for individual teams to ship low-quality stuff just because the next release train was a long and/or unpredictable time in the future.
It just seems ridiculous to me to have 4 major releases in ‘17 alone
Hm, why is that ridiculous? Do you just mean in terms of having "breaking changes" every 3 months? I guess I've never heard of someone bit by this... they'd have to be going out of their way to force a downgrade to trigger breakage from this, no?
Minor number is incremented whenever.
The number that is most important is the third number, the four digit build number, which increments monotonically and never resets. That is a more meaningful number than the first two, IMO anyways.