I like the idea, mostly. It seems like, generally speaking, FreeCAD is at a stage where there's a relatively big to-do list versus the developer*hours available. So, I mainly see crash reporting as a tool that could be good for catching new crashes early - like the one mentioned in the LibreOffice writeup - as opposed to another pile of to-do items.
It could also be interesting to be able to correlate results from something like this, with crashes reported in the tracker. That way, we could get the context that Yorik talked about, plus some idea as to how common the bug is in the field.
That said, I think Yorik's concern about it being another developer time suck is completely valid (and, "hundreds" might be a bit optimistic!
). I think it would be good if we used it like we use the Coverity reports, but maybe not so good if it resulted in increased forum noise for example. -Ian-