The crash occurs in the exception destructor. I could get it crash running compliance tests suite with wrong credentials, i.e. when connection method throws the exception. Other testsuites does not do, and I kinda failed to create a standalone test.
The reason is seemingly this pure Windows thing, when object is created in dll, and destructed in application(or vice versa). Making sure that copyconstructor exists only on the library side solved the problem.