Crash when using jack_load with an invalid internal client name twice

[falkTX]

jack_load is causing JACK1 to crash when called twice with a random name. example:

falktx@falkTX-Laptop:~$ jack_load meh
could not load jack_load, status = 0x81
falktx@falkTX-Laptop:~$ jack_load meh
cannot read server event (Success)
cannot continue execution of the processing graph (Bad file descriptor)
graph error - calling shutdown handler
cannot read result for request type 20 from server (No such file or directory)
unique internal client name `meh' assigned
falktx@falkTX-Laptop:~$ cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)

the "invalid" name doesn't need to be the same twice. example:

falktx@falkTX-Laptop:~$ jack_load 1st_somename
could not load jack_load, status = 0x81
falktx@falkTX-Laptop:~$ jack_load 2nd_another
cannot read server event (Success)
cannot continue execution of the processing graph (Bad file descriptor)
graph error - calling shutdown handler
cannot read result for request type 20 from server (No such file or directory)
unique internal client name `2nd_another' assigned
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)

[alextone]

I can reproduce this.

Alex.

[jdek]

Does anyone know if this is still an issue, and what operating systems/versions of JACK it still affects?