The Rusty guys at Microsoft are messing around with WinDbg 🙃
After stopping the debugging process, the DbgEng engine fails to release all objects, preventing a second dump file from being opened.
A golden rule: Always release what you allocate.
While building an automated analysis tool, I spent the whole day scratching my head over this bug in the latest WinDbg version 🤯
ALT Windbg leak - not release all handles after stop debugging