On Mon, Apr 14, 2025 at 06:48:32PM +0930, Robins Tharakan wrote:
> I didn't see any disk errors / memtest returned nothing / machine uses
> stock gcc (v12.2.0-14 - Ubuntu bookworm).
>
> I could reproduce this at will until this morning but not any more. A fresh
> git clone and compile in another folder on the same machine proved that the
> machine is okay, so my current guess is that I fell victim to not doing a
> 'git clean -xdf' when I was double-checking (before reporting). In most of
> my reports I try to triage the commit (which ensures this doesn't happen) -
> but I had to bypass that step this time since this was not a simple repro.
>
> Apologies for the noise, and once again thanks for taking a look.
FWIW, I've been puzzled by your report here, and also run similar
workloads on HEAD with an aggressive autovacuum setup to stress more
the code paths you have mentioned in your backtraces. That could be a
lack of luck because of a lack of friction with several concurrent
actions required, of course, but I've not been able to see your
problem. :/
--
Michael