https://bugs.winehq.org/show_bug.cgi?id=44600
--- Comment #4 from Fan gang fan.gang.cn@gmail.com --- (In reply to Nikolay Sivov from comment #3)
They are valid in theory, but not important in practice, and don't affect end users. See https://www.winehq.org/pipermail/wine-devel/2018-February/123267.html.
I agree that they are not important. But if the question has binary options (fix or not fix). I will still stick to they should be fixed, even in a less prioritized way.
Somebody has asked a similar question on StackOverflow. All the top voted answers suggest closing the resource anyway.
I copied one here.
"It depends on the operating system. The majority of modern (and all major) operating systems will free memory not freed by the program when it ends.
Relying on this is bad practice and it is better to free it explicitly. The issue isn't just that your code looks bad. You may decide you want to integrate your small program into a larger, long running one. Then a while later you have to spend hours tracking down memory leaks. Relying on a feature of an operating system also makes the code less portable."
The link:
https://stackoverflow.com/questions/2213627/when-you-exit-a-c-application-is...