Annoying, ain’t it? That specific problem is usually to do with Memory (not having enough).
Basically, if something like this happens and you’re using the GUI (as you obviously are), the first thing I’d try is rebooting your PC then as soon as you’re back in control don’t open anything (a web browser like Chrome eats memory for example). Just start DAE and try again and see if that fixes the problem (usually does).
Note that simply closing Chrome and trying DAE again is not the same thing as never starting Chrome in the first place…
If you looked in the log file you’d actually see it crashing (not always, but often) - the problem is that DAE’s GUI does nothing to recover from this situation - instead it just keeps on counting down, eventually going negative.
If the restart + run DAE trick don’t work then the next option is to use the command-line version - you even get to watch it crash if you’re unlucky enough / do it on purpose (huge image with huge chunks usually does the trick). Of course by using the CLI version you’re using even less memory.
DAE needs real memory available, the more the better - your swap file can help a little but only a little (eventually it won’t have anything it can swap out)
Personally I’ve got a lot of dev stuff on my main PC so usually hand off DAE stuff to another machine, the Mac for anything I want reasonably soon - which reminds me… Pi 4 is on Yira - almost finished it’s run