Can't have been much, as the Chrome project is 20+ years old and LLMs have only recently become a thing; they did not slacken their code review and testing practices with the advent of LLM code generators. And I doubt they do much development on the affected areas at the moment, they mention a 13 year old issue for example.

But it's an open source project, you can go and figure out whether your assertion is correct.

▲

lbrito 4 hours ago | parent | next [-]

>Can't have been much, as the Chrome project is 20+ years old and LLMs have only recently become a thing

That's not a great argument. GPT3.5 was launched over 4 years ago, so that's already significant compared to Chrome's age. LLMs notoriously also produce more verbose code than a human, so its not out of question that it might produce 5x more bugs on average given the same time frame.

▲

goldenarm 10 hours ago | parent | prev [-]

The single 13yo issue is anecdata.

They obviously have the full git blame statistics but chose not to include them in the blog post, which is a bit concerning.

	▲	rpdillon 2 hours ago \| parent [-]
		It's weird to assume that this is all smoke and mirrors where AI is fixing AI's bugs. When we dove into the rsync issue, what was happening is that AI was revealing bugs that had been previously unknown, resulting in the need to fix them. I would be stunned if that were not the case here.