Not closing properly after error

[pantropia]

Describe the bug
When the app has been closed after a crash I've noticed in Task Manager that the app is still running and using a lot of memory. It does eventually close if I do 'end task' but it takes quite a while to do so.

To Reproduce
Steps to reproduce the behavior:

1. Scan a folder with a lot of files in it
2. Get a memory error
3. Close app with x at top right
4. Look at task manager - see DG still using at least 50% of the memory
5. End task
6. Wait

Expected behavior
App should close when x clicked

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Windows 11 23H2 build 22631.3155 , Ryzen 7, 64GB RAM
• Version 4.3.1

Additional context
I've been using DupeGuru successfully for years on both PC and Mac but started having problems scanning external drives with my little laptop last year. Performance was less of a concern than price when the laptop was bought so I assumed the issues were because of its lack of power and drive space, so after I moved and had more cash available I bought a reasonably powerful desktop with an nvme c: drive and a pair of 20TB spinning sata drives set up raid1 to be my file store - this is where the folders I'm scanning are located.
I thought all would be well on the new machine, but I've had the memory issue trying to scan one of the folders, the issue where it gets stuck on 'fiddling with results' for days (a power cut put an end to that and a subsequent attempt at the same scan had a memory crash) and it's also not finding some definite duplicates - I have been using BeyondCompare to copy files of particular types to folders (maintaining the original folder structure in the new location) to make them easier to sort through. I set the new directory as reference and the source as Normal and DG found plenty of duplicates but when I ran BC again expecting to see no matches in the two identical folder structures (as DG should have removed them) a lot were still there. And no, they shouldn't have been excluded due to size. I'll need to spend some more time getting details of that one, however, as I didn't have debugging turned on.