Bug #47424 mysql server does not detect dead clients, if they use shared memory protocol

Description:
I start mysql server with enabled shared memory protocol (use "shared-memory"
in my.ini file).
Then I start command line client with
mysql -uroot --protocol=memory

Then I kill command line client with 
taskkill /im mysql.exe /f

I attach debugger to mysqld.exe and see a thread that stucks (forever) in 
vio_read_shared_memory().

I start another shared memory client and kill it. Now there are 2 threads that stuck (forever) in vio_read_shared_memory().
In addition, process explorer , shows server opens a number of event and section objects that are never released.

How to repeat:
Follow the steps in description.

Suggested fix:
Currently, server does not have an ability to track whether client is alive. 
Just an idea: if client could pass its PID when connecting, then server would be able to check if process is still alive.

Thank you for the problem report. Verified just as described with 5.1.38 on XP.

No more interested in having it fixed