Lead on Happy Ghast causes crash with exit code -1073741819

I tried this but it didn’t happen for me

I can't confirm this, but if you could provide more information on how to reproduce the bug, that would be great!

We do not have enough information to find the cause of this issue.

Please attach the crash report found in minecraft/crash-reports/crash-<DATE>-client.txt here.
If you cannot find a crash report, please attach the full launcher log found in minecraft/launcher_log.txt.

This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines -- 💬 Community Support -- 📧 Mojang Support (Technical Issues) -- 📧 Microsoft Support (Account Issues) -- ✍️ Feedback and Suggestions -- 📖 Game Wiki

To reproduce it I just attached a lead to the Happy Ghast and started flying arround in creative mode.

I cannot reproduce this issue. Is there any specific setup required for this issue to occur? Please provide a clear and consistent way to get this crash happen and describe it in the description.

When I leash a happy ghast and fly around with it, nothing happens to my game.

To be honest I don’t really know (I tried to reproduce it on another pc but it doesn’t crash)
As for how I created it:
/summon happy_ghast (I then put an harnest to it)

/attribute @n[type=happy_ghast] flying_speed base set 10

/attribute @n[type=happy_ghast] movement_speed base set 10

(this way you can have the exact same Ghast as I have, but the values doesn’t change anything on the Ghast, he has the same speed)

And then use a lead on him and fly around.

But as I said I can’t reproduce it on my other PC, so giving you the specs of the PC on which it crashed may be helpful:
GPU: AMD rx 6750xt
CPU: AMD Ryzen 7 7800x3D
RAM: 32GB DDR5 (2GB on Minecraft)

The game was running on a NVME SSD.

I don’t know why this has happened to me twice on my computer but not on the other one, I you have any other question please do.

Could you please confirm whether this issue persists in version 1.21.6-pre3? If so, please attach the crash report found in minecraft/crash-reports/crash-<DATE>-client.txt.

This ticket will automatically reopen when you reply.