This seems to be an issue with locking a weak_ptr. By debugging i've found, that the weak_ptr being locked is null, which causes a segfault. Since MSVC and gcc/clang have different implementations of the standard library, it might be related to that. I've seen that there is a null-check for a pointer, but only after locking. I believe this would be a simple fix, simply by checking for null before locking the weak_ptr.
@Tom Gray my debian install where the crash occured is on libstdc+6.0.25. My personal computer, which has libstdc6.0.28 also crashes. I don't think this is an issue with any specific libstdc+ version.
This seems to be an issue with locking a weak_ptr. By debugging i've found, that the weak_ptr being locked is null, which causes a segfault. Since MSVC and gcc/clang have different implementations of the standard library, it might be related to that. I've seen that there is a null-check for a pointer, but only after locking. I believe this would be a simple fix, simply by checking for null before locking the weak_ptr.