常年霸占ios的bugly榜首的一个crash 在ios退出时发生
参考之前的论坛文章 IOS退出必现崩溃的分析及临时解决办法 猜测需要把s_cacheFontData改成指针 但是这个指针在哪里主动去delete又成了问题 也许用智能指针会好 想等一个官方答案
官方大大可以路过看一眼吗？ 调用栈如下
std::__1::__hash_iterator<std::__1::__hash_node<std::__1::__hash_value_type<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, cocos2d::_DataRef>, void*>*> std::__1::__hash_table<std::__1::__hash_value_type<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, cocos2d::_DataRef>, std::__1::__unordered_map_hasher<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::__hash_value_type<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, cocos2d::_DataRef>, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, true>, std::__1::__unordered_map_equal<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::__hash_value_type<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, cocos2d::_DataRef>, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, true>, std::__1::allocator<std::__1::__hash_value_type<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, cocos2d::_DataRef> > >::find<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&) + 40
cocos2d::FontFreeType::~FontFreeType() + 392
cocos2d::FontFreeType::~FontFreeType() + 12
cocos2d::AutoreleasePool::clear() + 100
cocos2d::AutoreleasePool::~AutoreleasePool() + 20
cocos2d::PoolManager::~PoolManager() + 44
cocos2d::PoolManager::destroyInstance() + 28
cocos2d::ApplicationProtocol::~ApplicationProtocol() + 36