I’m on Mac OSX 10.11.6 (ElCap), using Manager 16.11.80 (I can’t go back to 57 since the data file is now with the later version).
Following the above steps I get no crash. My manager has been rock solid for a while, the last crash I recall was to do with the print dialog. Nothing else since.
@HeritageArts, when it comes to the developer tool user, it’s just you (if you are also the administrator). If not, and have you administrator access, just enter those credentials. The developer tools require admin access to do their debugging. However, since you don’t have the source code (ie it’s not your project you are debugging) you are likely NOT to get anything useful from it. Although I WOULD recommend giving it a go since it may present a dialog box with the mono/manager module that has caused the grief.
Notwithstanding this, the generic apple error report * that get’s generated should provide enough usable information for @lubos to use. I know it’s lengthy, but you could always copy and paste it and send it to his email, or drop it into a http://pastebin.com/ type service. The information in it is anonymised, although as you can see in my example, I have removed just the UUIDs, just because
This information, may or may not help lubos get to the bottom of it. This one here is one generated just from the print dialog which I can force by trying to change the scale to 0%
* although I say “generic apple error report”, I’m not sure if this is more advanced since I have the debugging tools installed or not. I suspect it IS generic (non-XCode specific), but I’m not sure.