Bizarre Stack Overflow when utilizing Default trait or ..default() to initialize components

[jaydevelopsstuff]

Bevy version

0.13.1

Relevant system information

• Rust version 1.77.1 (from cargo --version)
• M1 Macbook Air MacOS Sonoma 14.0 (23A344)

What you did

In my own project I was trying to create a Component that implemented the Default trait for my own purposes and ran into a stack overflow when spawning an entity bundle with the component. There was no real distinguishable cause.

After commenting out some code I found it had to with implementing and using the Default trait on one of my own Components. This looked like it could be an issue with Bevy so I created an MRE using just MinimalPlugins, so headless Bevy and low and behold the stack overflow persists.

What went wrong

I'd expect initializing via the Default trait or using ..default(), to well, not cause any issues and work as you'd expect the Default trait to work. But instead it resulted in a stack overflow error. These overflows seem to originate from compute task pool threads based on the resulting errors.

This does not seem to be related to GUI at all as it still occurs with only MinimalPlugins.

Additional information

MRE Repo

Possibly related issue: #8406

The only workaround I've found is just to straight-up not use the Default trait or ..default() to initialize in-house Components when creating an entity.

Also just for clarity, when I say in-house I mean anything not in Bevy's codebase.

[james7132]

This seems to be caused by the fact that default calls Default::default, which will recursively called until the the stack overflows. See #8879. Closing this out as a user error since we already have an issue about silencing the warning.