Re: [2/3] kernel32: Terminate threads before unloading DLLs on process exit.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
If it's not yet time to make this change please let me know what else needs to be tested/fixed/investigated.
The heap behavior would need testing, since freeing memory is probably the most common thing done in a detach routine. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
If it's not yet time to make this change please let me know what else needs to be tested/fixed/investigated.
The heap behavior would need testing, since freeing memory is probably the most common thing done in a detach routine.
You mean testing whether heap lock is held during process exit and/or dll detach notification is being sent? -- Dmitry.
Dmitry Timoshkov <dmitry(a)baikal.ru> writes:
Alexandre Julliard <julliard(a)winehq.org> wrote:
If it's not yet time to make this change please let me know what else needs to be tested/fixed/investigated.
The heap behavior would need testing, since freeing memory is probably the most common thing done in a detach routine.
You mean testing whether heap lock is held during process exit and/or dll detach notification is being sent?
Not really, more like what happens if one of the terminated threads was holding the lock. -- Alexandre Julliard julliard(a)winehq.org
Alexandre Julliard <julliard(a)winehq.org> wrote:
If it's not yet time to make this change please let me know what else needs to be tested/fixed/investigated.
The heap behavior would need testing, since freeing memory is probably the most common thing done in a detach routine.
You mean testing whether heap lock is held during process exit and/or dll detach notification is being sent?
Not really, more like what happens if one of the terminated threads was holding the lock.
Yeah, I realized that once I sent a reply. -- Dmitry.
participants (2)
-
Alexandre Julliard -
Dmitry Timoshkov