Johannes,
Just tried to launch it once more this morning: no more crash. Even though it crashed around 10x in a row.
Things that changed:
1) I downloaded the "south-building" dataset and did the full flow (incl reconstruction) on that one. That worked fine. And then I went for bed.
2) I had a second instance of Colmap running at the same time of the crashins. That instance was running an exhaustive feature matching on a different project. That was completed sometime this morning.
When I open the "previously crashing" project now, the reconstruction starts normally. : (
I will, later today, check whether Time Machine can still get me my original DB from the time it was crashing. I will check whether I can get it back into crashing mode.
I copied the full "Apple Crash Report". Can that be of any use?
Sidenote: The other instance (as mentioned above) completed the exhaustive feature matching on the same photo set (to compare the results). I started the reconstruction. It only seems to have found roughly 30 of the >1000 camera positions. As can be expected the results not as it needs to be.
Note on the note: I did run the same photo set through Agisoft before: the sparce cloud is very fine there. So the dataset should be good enough to do a reconstruction (I hope).
Since the documentation set does not explain each of the settings in detail, I did not fiddle around with the setting yet to see how to improve this.
Also for this one, if it is useful for you to get extra info, just let me know.
While typing this mail the "now-not-crashing-anymore" project did do some of the reconstruction already. You can see (attached image) is has already found many more camera positions.
Top one = crashing before - sequential feature matching (still running)
Bottom one = exhaustive matching (stopped reconstruction). Start reconstruction is disabled now, since the SW seems to find it OK. : )
Regards
Johan