mapillary / mapillary/OpenSfM

Segmentation fault while running reconstruction

Open
#883 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
3.8k
Forks
899
PR merge metrics
No merged PRs in 30d

Description

I have installed all the dependencies and am able to import opensfm successfully. However, when I try to run the berlin example as given in the documentation, I get a segmentation fault as follows:

2022-03-17 14:45:18,541 INFO: Starting incremental reconstruction
2022-03-17 14:45:21,804 INFO: Starting reconstruction with 01.jpg and 02.jpg
2022-03-17 14:45:21,878 INFO: Two-view reconstruction inliers: 1267 / 1268
2022-03-17 14:45:21,941 INFO: Triangulated: 1232
2022-03-17 14:45:21,959 DEBUG: Ceres Solver Report: Iterations: 3, Initial cost: 1.635496e+01, Final cost: 1.434942e+01, Termination: CONVERGENCE
2022-03-17 14:45:22,043 DEBUG: Ceres Solver Report: Iterations: 3, Initial cost: 1.475086e+01, Final cost: 1.399629e+01, Termination: CONVERGENCE
2022-03-17 14:45:22,214 DEBUG: Ceres Solver Report: Iterations: 20, Initial cost: 3.532901e+01, Final cost: 2.703779e+01, Termination: CONVERGENCE
2022-03-17 14:45:22,217 INFO: Removed outliers: 0
2022-03-17 14:45:22,218 INFO: -------------------------------------------------------
Segmentation fault

Any help in this? I am using centOS.

Thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Berlin example on CentOS using the documented command and capture the complete environment and dependency details. Inspect the incremental reconstruction stage immediately before the segmentation fault, using the logged two-view reconstruction and Ceres output to narrow the failure. Done means identifying a reproducible cause and confirming that the example completes without a segmentation fault.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-vision
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.