https://bugs.winehq.org/show_bug.cgi?id=44816
--- Comment #2 from Zebediah Figura z.figura12@gmail.com --- (In reply to Zebediah Figura from comment #1)
I'm guessing the double-free results from the kernel freeing the thread's stack once it's terminated (I'm not sure, and it's hard to be sure just from skimming the kernel code, but it seems like the only sane thing to do?) since we certainly don't free it ourselves.
Actually, on further testing, it seems the kernel doesn't free anything. So what gives? How could there possibly be a double free here?