3m-softHello!
Since last day, we get a lot of crashes from our customers with the following call stack:
Thread 1 Crashed:0 com.***.*** 0x000000010fa5d72c TA_LIB_NS::Hardware::IsVM() + 421 com.***.*** 0x000000010fa71f2c Trial::HIDFuzzyMatches() + 3182 com.***.*** 0x000000010fa71a9e Trial::LoadVerifiedTrial(std::__1::basic_ifstream<char, std::__1::char_traits<char> >&) + 2643 com.***.*** 0x000000010fa6f0f4 Trial::LoadTrial() + 3404 com.***.*** 0x000000010fa72720 Trial::IsTrialExpired(long*) + 305 com.***.*** 0x000000010fa7d93a TrialManager::do_work() + 8546 com.***.*** 0x000000010fa5de50 TA_LIB_NS::Heartbeat::hb_tick(boost::system::error_code const&) + 427 com.***.*** 0x000000010fa60eaa boost::asio::detail::wait_handler<boost::_bi::bind_t<void, boost::_mfi::mf1<void, TA_LIB_NS::Heartbeat, boost::system::error_code const&>, boost::_bi::list2<boost::_bi::value<TA_LIB_NS::Heartbeat*>, boost::arg<1> (*)()> >, boost::asio::detail::io_object_executor<boost::asio::executor> >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) + 1748 com.***.*** 0x000000010fa5f851 boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 4779 com.***.*** 0x000000010fa5bd4a boost::asio::detail::scheduler::run(boost::system::error_code&) + 25210 com.***.*** 0x000000010fa5a477 TA_LIB_NS::GlobalVars::runIOService() + 5111 com.***.*** 0x000000010fad8088 0x10f964000 + 152384812 libsystem_pthread.dylib 0x00007fff7130f2eb _pthread_body + 12613 libsystem_pthread.dylib 0x00007fff71312249 _pthread_start + 6614 libsystem_pthread.dylib 0x00007fff7130e40d thread_start + 13
Crashes occur in the following OS: Mac OS X 10.13.x, Mac OS X 10.14.x, Mac OS X 10.15.xTurboActivate library has version 4.1.9Please advice what does it mean?
First, use the latest version. Then try again.
Secondly, if youre using the static library, then use the dynamic library.
Lastly, what programming language are you using? Did you trap all exceptions (even ones we catch internally?) if so, dont do that. Thats broken behavior.
3m-softThis refers to a command utility where some crashes are raised. There we use Clang and we do not trap exceptions.
However, we have noted that a hacker group cracked our product yesterday and It was revealed that these crashes came from cracked version users. Thus, we believe that the nature of these crashes are not subject to our responsibility. Thank you for a quick turnaround.
