[Boost-users] [filesystem] std::bad_alloc during dll initialization when migrating to filesystem v3

Hi Guys, I'm currently migrating our system consisting of multiple dll's and and executable to filesystem v3. The first two dll's that use boost::filesystem load ok, but the third fails with std::bad_alloc in the locale copy constructor called from default_locale during the construction of dot_path. I don't know if it's relevant, but we usually work with char while filesystem uses wchar_t for BOOST_WINDOWS_API Rgds Richard