beaTunes News

The new CrashReporter built into the latest beaTunes versions already provides valuable info. It looks like a number of users experience crashes that might have to do with Hear. If you see a couple of lines like these in your crashlog,

Thread 23 Crashed:
0   com.joesoft.hal                0x0e36eced osp_plugin::osp_plugin() + 13
1   com.joesoft.hal                0x0e377d2d std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, 

it's possible that the crash was caused by a plugin in /Library/Audio/Plug-Ins/HAL. Users have told me it might be the Hear.plugin. Removing the plugin probably solves the problem. I have not been able to verify this myself yet, but would appreciate some feedback.

Thanks!

(Apparently we are not the only ones fighting this stuff: AppJacked 2)

Update:Looks very much like Hear is the culprit. The telltale sign is very high memory consumption. Note that its not enough to simply drag the Hear application to the trash. To actually remove the plugin, follow the uninstall directions. You have to run Hear to call Uninstall from its application menu. Alternatively, you can simply remove the file /Library/Audio/Plug-Ins/HAL/Hear.plugin

Labels: AppJacked, Crash