https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #101 from documentfoundat...@lpeters.de ---
MacOS has built-in tools for checking heap corruption.
See:
https://developer.apple.com/library/content/technotes/tn2124/_index.html
(look at "Enabling Debugging
https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #100 from Alex Thurgood ---
(In reply to Michael Meeks from comment #99)
> strongly suggests a generic heap corruption; the question is - do we have a
> valgrind equivalent on Mac to try to find that
https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #99 from Michael Meeks ---
Thanks Norbert:
2268 free_small (in libsystem_malloc.dylib) + 721 [0x7fffa73e7c66]
2268 small_free_list_remove_ptr_no_clear (in libsystem_malloc.dylib) + 766
https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #98 from tanel ---
Another confirm, MBP 2011, non-Retina. Setting color profile to "Color LCD"
(which is default for built-in display) or "Generic RGB" works, the calibrated
ones provided by the external monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=100994
--- Comment #97 from Luca Aluffi ---
The color space I am using on MacBook Pro mid 2010 with discrete graphic card
was already at its default (it is named "LCD display") when crash started to
occur.
In my case
https://bugs.documentfoundation.org/show_bug.cgi?id=100994
Norbert Thiebaud changed:
What|Removed |Added
Summary|Freeze / Crash on first |Freeze /