Robin Gareus
36f6aa9356
This is not a real fix; just a stop-gap for the worst offender. iostream on OSX is not thread safe. Sadly no crash report so far managed to catch the 2nd thread in action. looks like the GUI thread is preempted, 2nd thread succeeds, and the crash occurs later). see also https://discussions.apple.com/thread/3479591 crash in s << c->internal_to_user (c->get_value ()); ardour-4.1.335(5000,0x7fff777f5300) malloc: *** error for object 0x7fe2f3e06170: pointer being freed was not allocated 1 libsystem_c.dylib abort + 129 2 libsystem_malloc.dylib free + 428 3 libsystem_c.dylib __numeric_load_locale + 544 4 libsystem_c.dylib loadlocale + 216 5 libstdc++.6.dylib std::__convert_from_v(int* const&, char*, int, char const*, ...) + 193 6 libstdc++.6.dylib std::ostreambuf_iterator<char, std::char_traits<char> > std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::_M_insert_float<double>(std::ostreambuf_iterator<char, std::char_traits<char> >, std::ios_base&, char, char, double) const + 193 7 libstdc++.6.dylib std::ostream& std::ostream::_M_insert<double>(double) + 221 8 ardour-4.1.335 ProcessorEntry::Control::set_tooltip() + 854 (processor_box.cc:578) 9 ardour-4.1.335 ProcessorEntry::Control::control_changed() + 446 (processor_box.cc:637) 10 ibpbd.dylib PBD::StandardTimer::on_elapsed() |
||
|---|---|---|
| cfgtool | ||
| doc | ||
| export | ||
| gtk2_ardour | ||
| headless | ||
| icons | ||
| libs | ||
| mcp | ||
| midi_maps | ||
| msvc_extra_headers | ||
| MSVCardour3 | ||
| MSVCMixbus3 | ||
| MSVCvst_scan | ||
| patches | ||
| patchfiles | ||
| templates | ||
| tools | ||
| vst | ||
| .dir-locals.el | ||
| .gitignore | ||
| ardour-3.ttl | ||
| ardour.1 | ||
| ardour.1.es | ||
| ardour.1.fr | ||
| ardour.1.ru | ||
| ardour.dox | ||
| COPYING | ||
| foo.cc | ||
| instant.xml | ||
| instant.xml.sae | ||
| Makefile | ||
| msvc32-fixup.pl | ||
| PACKAGER_README | ||
| README | ||
| system_config | ||
| testfile.flac | ||
| testfile.ogg | ||
| TRANSLATORS | ||
| waf | ||
| wscript | ||
Please see the Ardour web site at http://ardour.org/ for all documentation..
For information on building ardour:
http://ardour.org/development.html