[RPC] Reproducer for RPC session deadlock

[KJlaccHoeUM9l]

The problem is that the created object for the PRC session was not destroyed when it went out of scope, which caused the tracker to think that the device was busy, and therefore it was impossible to create a new session.

The above code demonstrates this behavior and shows the reason why this is happening.

Cause:
Three fields are created in the special class SomeHolder:

• remote_session - session, which should be destroyed along with the object SomeHolder
• deadlock_field - a lambda function that does not destroy the SomeHolder object
• field_which_needed_for_deadlock - the field that is needed in order for the lambda to be created so that the object is not destroyed (circular reference?)

If you remove the field_which_needed_for_deadlock field, there will be no deadlock.